-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
$ref to definitions inside “source” or “with” parts of $merge is not supported #28
Comments
Please add a specific example that you expect to work. |
Something like :
|
yes, definitions have to be outside of the merge (and you can use merge inside definitions |
Is there an example anywhere of how this looks? I've tried the following (mock example) but it doesn't seem to work. Do I have
|
Sorry but this is nothing logic. I did want to merge to entities, if I need
to put definitions in another section, I do the merge myself ... And in the
last case it's the same, to have définitions of a $ref is understandable as
$ref should declare its own definitions.
Sorry but Not Logic.
Le jeu. 14 nov. 2019 03:28, Nathan Winch <[email protected]> a
écrit :
… yes, definitions have to be outside of the merge (and you can use merge
inside definitions
Is there any example anywhere of how this looks? I've tried the following
(mock example) but it doesn't seem to work. Do I have definitions at the
correct level (parallel to $merge) ?
{
"id": "lixi-internal-request-custom",
"$merge": {
"source": { "$ref": "lixi-internal-request" },
"with": {
"properties": {}
}
},
"definitions": {
"ID": {
"pattern": "^[a-zA-Z0-9_][a-zA-Z0-9-_.]*$"
}
}
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJU4UFQSW5VW3MO23RN4XNTQTSZWHANCNFSM4GOOWL4A>
.
|
Hi,
When the "with" object contains definitions (like '"$ref": "#/definitions/JwtConfig"'), ajv throws an error.
I need to move the "with" "definitions" property to the main object :
I think it's an issue :)
Regards
The text was updated successfully, but these errors were encountered: