You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
a: 1 (number, required) - One
b: 2 (number, required) - Two
create.md
<!-- include(./base.md) -->
c: 3 (number, required) - Three
d: 4 (number, required) - Four
create-response.md
<!-- include(./create.md) -->
extra: extra (string, required) - Something extra
-d
So now I would expect to have a response object like this:
{a: 1,b: 2,c: 3,extra: "Extra"}
However I have found no way to remove an object key that was already defined somewhere "on top".
You can overwrite d to other value (null, undefined), but not remove it completely.
Currently -d results in
d: ""
Thank you for consideration.
BTW - great work, I really enjoy using this standard!
The text was updated successfully, but these errors were encountered:
I think it would be beneficial in terms of structure reusability if there was a way to remove keys from schemas (data structures).
I'm defining request/response objects like data structures
And in files I have something like this:
base.md
create.md
<!-- include(./base.md) --> c: 3 (number, required) - Three d: 4 (number, required) - Four
create-response.md
<!-- include(./create.md) --> extra: extra (string, required) - Something extra -d
So now I would expect to have a response object like this:
However I have found no way to remove an object key that was already defined somewhere "on top".
You can overwrite
d
to other value (null, undefined), but not remove it completely.Currently
-d
results inThank you for consideration.
BTW - great work, I really enjoy using this standard!
The text was updated successfully, but these errors were encountered: