-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
refactor: init custom parser functionality #489
refactor: init custom parser functionality #489
Conversation
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.
No tests? 😄
without tests, I will add them soon.
Ah 😆
import { xParserOriginalTraits } from '../constants'; | ||
import { mergePatch } from '../utils'; | ||
|
||
const v2TraitPaths = [ |
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.
v2
means v2
of the spec here? If so, shall we extract the paths to their own files so we can do the same for v3
spec ?
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.
We will have only 2 custom operations and I don't think so that we should split them to separate files. We can do it later, if we will have more logic for each version.
11aca9a
to
466e6cd
Compare
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.
LGTM!
Kudos, SonarCloud Quality Gate passed! |
/rtm |
Description
registerSchemaParser
etc.applyTraits
orparseSchemas
.Related issue(s)
Part of #481
Part of #482