-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: Allow non conflicting path methods to merge #78
base: main
Are you sure you want to change the base?
Feat: Allow non conflicting path methods to merge #78
Conversation
This also includes my previous MR for deep merging security schemes |
|
||
export function expectErrorType(result: MergeResult, type: ErrorType): void { | ||
if (isErrorResult(result)) { | ||
expect(result.type).toEqual(type); | ||
} else { | ||
fail(`Expected an error, but instead got: ${JSON.stringify(result, null, 2)}`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fail no longer exists in Jest v27+
} | ||
} | ||
|
||
export function expectMergeResult(actual: MergeResult, expected: MergeResult): void { | ||
if(isErrorResult(actual)) { | ||
fail(`We expected to have a successful merge and instead got: ${JSON.stringify(actual, null, 2)}`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
Hi, did you find any issue to not merge this PR ? |
@robertmassaioli Can this be merge? |
any chance this could be merged ? |
@robertmassaioli Would be great if we could merge this |
There is an open TODO in the queue to allow non-conflicting methods to merge in to the same path, so I've completed it.
The code may not be entirely the neatest (its a little bit of a hack), but open to suggestions.