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

k6: use camelCase to encode ingredient restrictions #24

Merged
merged 1 commit into from
Aug 28, 2023
Merged

Conversation

roobre
Copy link
Collaborator

@roobre roobre commented Aug 28, 2023

In #9 we made a change to the backend to format JSON keys as camelCase, as the frontend was sending them in camel case. However, k6 scripts were sending sneak_case instead.

This PR changes k6 script to use camel case as well.

@roobre roobre requested review from dgzlopes and ppcano August 28, 2023 09:27
@roobre roobre merged commit dec4d1a into main Aug 28, 2023
1 check passed
@dgzlopes dgzlopes deleted the camelCase branch August 28, 2023 11:50
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.

None yet

3 participants