Fix: Remove spec 3 references keys in imports for TypeScript

[smasala]

PR checklist

• Read the contribution guidelines.
• Filed the PR against the correct branch: master
• Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Sanitizes model names by removing anyOf and oneOf spec reference keys in model imports.

Fixes: #1913

@TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09) @macjohnny (2018/01) @nicokoenig (2018/09) @topce (2018/10)

[macjohnny]

LGTM

[smasala]

Override names - requires: #2046

[smasala]

@wing328 don't think we are going to be able to create a sensible anyOf|oneOf implementation with the current template injection methodology... see file changes. Output:

import { FirstRuleDefinition | SecondRuleDefinition } from './firstRuleDefinitionSecondRuleDefinition';

export interface CustomRule { 
    ruleId?: string | null;
    definition?: FirstRuleDefinition | SecondRuleDefinition | null;
}

I think we need to approach this in a new manner.
The imports need to be an array and the types shouldn't be manipulated with strings to get the desired output of:

import { FirstRuleDefinition} from './firstRuleDefinition';
import { SecondRuleDefinition } from './secondRuleDefinition';

export interface CustomRule { 
    ruleId?: string | null;
    definition?: FirstRuleDefinition | SecondRuleDefinition | null;
}

[wing328]

Let's have another chat in the coming week when you've time.

[smasala]

@wing328 updated the solution. Works for TS

[macjohnny]

@smasala could you please fix the merge conflicts?

[macjohnny]

@smasala the CI is failing, can you have a look at it?

[macjohnny]

LGTM

[AlexanderSchiff]

Hello, is there any chance you could release this to the NPM package? as a minor release? Thanks! @wing328 @macjohnny

[macjohnny]

this will be released in 4.1.0, probably this week