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

Serializer vs mutation keys expectation, sync issue #109

Open
sanjarcode opened this issue Jan 2, 2024 · 0 comments
Open

Serializer vs mutation keys expectation, sync issue #109

sanjarcode opened this issue Jan 2, 2024 · 0 comments
Assignees

Comments

@sanjarcode
Copy link
Member

sanjarcode commented Jan 2, 2024

Supose I call a "user contacts" API in my app, the BE sends this.
The keys here we decided by the frontend person for ease in frontend code.

{ id: 59, name: "John Doe", email: "abcdefgmail.com", phone: null }

but it expects the following for a PUT/POST. It expects this because it uses the keys (below) internally in BE

{ id: 59, name: "John Doe", email_address: "abcdefgmail.com", phone_number: null }

problem

Now whotf is going to manage this synching?
This is bad design, and it's not complex bad either.

fix

whats the fix here?

@sanjarcode sanjarcode self-assigned this Jan 2, 2024
@sanjarcode sanjarcode changed the title Serializer keys vs mutation keys expectation, sync issue Serializer vs mutation keys expectation, sync issue Jan 2, 2024
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

No branches or pull requests

1 participant