Skip to content
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(response-transformer) preserve empty arrays #4901

Merged
merged 1 commit into from
Aug 13, 2019

Conversation

kikito
Copy link
Member

@kikito kikito commented Aug 13, 2019

When a response contains an empty array and it gets transformed, the empty array should remain an empty array (and not get transformed into an empty cjson object).

Fixes #1208.

When a response contains an empty array and it gets transformed, the empty array should remain an empty array (and not get transformed into an empty cjson object).

Fixes #1208.
@kikito kikito force-pushed the fix/response-transformer-empty-arrays branch from 8da3066 to 454f09c Compare August 13, 2019 14:24
@hishamhm hishamhm merged commit e364354 into next Aug 13, 2019
@hishamhm hishamhm deleted the fix/response-transformer-empty-arrays branch August 13, 2019 16:21
@hishamhm hishamhm added this to the 1.3.0 milestone Aug 13, 2019
hishamhm pushed a commit that referenced this pull request Aug 15, 2019
When a response contains an empty array and it gets transformed, the empty array should remain an empty array (and not get transformed into an empty cjson object).

Fixes #1208.
fffonion pushed a commit that referenced this pull request Aug 31, 2022
#9186)

…'t be properly re-encoded as an array. Instead, it becomes an empty json object.

This PR fixes this issue. An empty json array will remain to be an empty json array after being decoded and re-encoded.

This is a sister PR to PR:

[#4901](#4901)

It contains a similar fix, but now to `request-transformer` (this plugin).

FTI-4205
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants