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
@romalytvynenko
When using JsonResource responses in combination with $wrap we can make very nice responses; except there is an issue when the $wrap key is set to a value which also contains within the array itself the "wrap" is getting ignored for documentation while the endpoint is still sending it out like so:
but when using a different wrapper key like test we get:
and if when wrapper key is still locale and the locale key within the array is changed to for instance current_locale we are getting expected results like so:
so there is a conflict while having keys with the same name in the data array and wrapper key; then the wrapper key looks to be ignored which shouldn't be the case
if more info is needed please let me know
The text was updated successfully, but these errors were encountered:
@romalytvynenko
When using JsonResource responses in combination with $wrap we can make very nice responses; except there is an issue when the $wrap key is set to a value which also contains within the array itself the "wrap" is getting ignored for documentation while the endpoint is still sending it out like so:
the endpoint/backend is providing this:
the LocaleResource looks like this:
when using the same key like above the result is:
but when using a different wrapper key like
test
we get:and if when wrapper key is still
locale
and thelocale
key within the array is changed to for instancecurrent_locale
we are getting expected results like so:so there is a conflict while having keys with the same name in the data array and wrapper key; then the wrapper key looks to be ignored which shouldn't be the case
if more info is needed please let me know
The text was updated successfully, but these errors were encountered: