-
Notifications
You must be signed in to change notification settings - Fork 66
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
[fix] Aliases are now allowed in path and query parameters #80
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.
can we add some tests that would have previously failed
.map(entry -> entry.getValue().visit( | ||
new TypeDefinitionParserVisitor(entry.getKey().name(), defaultPackage, typeResolver))) | ||
.collect(Collectors.toList())) | ||
.build(); | ||
.collect(toImmutableMap(td -> td.accept(TypeDefinitionVisitor.TYPE_NAME), td -> td)); |
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.
why can't we just use the regular collector
hey folks, can we please get a release with this? blocking /f/comments/pull/427 / /f/comments/pull/396 |
Happy to release but please try to avoid adding internal links to external github |
This fixes a regression introduced in #37 (release 4.0.1)
Fixes #61
Implementation
Add ConjureContextualValidator concept - when validating, it's also given a
DealiasingTypeVisitor
that can be used to find the de-aliased Type (it's traversed through the object definitions until you find a type that's not a reference type).The
DealiasingTypeVisitor
takes the parsed version of the conjure yml types block, in the form of aMap<TypeName, TypeDefinition>
, in order to resolve references.