Allow to override mapping of custom scalar to OpenAPI #1159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ardatan can you please review this PR? |
|
@Urigo @dotansimha how can we help to merge this faster? 🙏 |
jgartor
pushed a commit
to dataxquare/SOFA
that referenced
this pull request
May 4, 2023
* Allow to override mapping of custom scalar to OpenAPI * Trigger CI Co-authored-by: Arda TANRIKULU <ardatanrikulu@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current implementation, all custom scalars are mapped to
{ type: "object" }on OpenAPI. However,objectis not appropriate because, for example, aDatescalar is a string of the form"YYYYY-mm-dd".This PR implements the
customScalarsoption to control the type of custom scalars when mapping them to OpenAPI.