-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
refactor: mfe_context response to serialize object keys to camelcase #31930
Conversation
250c87c
to
3891ac8
Compare
8b401dc
to
7d79c18
Compare
e687c85
to
d52fc24
Compare
cdfa5c3
to
292c07e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one question that I asked, otherwise looks good.
10f27d1
to
97d94f3
Compare
97d94f3
to
ab61e66
Compare
ab61e66
to
87d76d9
Compare
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production. |
EdX Release Notice: This PR has been deployed to the production environment. |
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production. |
EdX Release Notice: This PR has been deployed to the production environment. |
* refactor: mfe_context response to serialize object keys to camelcase (#31930) * test: add tests for MFE Context API serializser (#32179) * fix: empty pipelineUserDetail object pipelineUserDetail object should be empty when pipeline is not running --------- Co-authored-by: Shahbaz Shabbir <32649010+shahbaz-arbisoft@users.noreply.github.com>
* refactor: mfe_context response to serialize object keys to camelcase (openedx#31930) * test: add tests for MFE Context API serializser (openedx#32179) * fix: empty pipelineUserDetail object pipelineUserDetail object should be empty when pipeline is not running --------- Co-authored-by: Shahbaz Shabbir <32649010+shahbaz-arbisoft@users.noreply.github.com>
This pull request modifies the serialization of the back-end response by converting the keys of objects to camelCase. By making this change, we can avoid the need to convert the keys to camelCase on the front-end and ensures that all related unit tests have been updated accordingly.
In order to prevent compatibility issues, it is necessary to remove any front-end code that converts keys from snake_case to camelCase format where it is required.
Ticket: VAN-1311