-
Notifications
You must be signed in to change notification settings - Fork 184
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
camelize keys #42
Comments
The way I am getting around this is:
It's not elegant at all. Seems like I cannot change |
Agreed. I really didn't like how I implemented that at all. The problem is I wanted to play it safe by passing a new object to each transform. I was encountering situations where I was able to break things if i mutated the wrong object (like So although, it looks like the transform is receiving the response. It's not. It's receiving a decoy. That's why changing references is messing up your evening. I started out on the immutable route, but after seeing how slow transforms were once you started passing large data (like file uploads), i opted for the solution you see now. |
@skellock makes sense. What do you suggest is the best way then? My solution works for now, but it's... not great. |
Ok @mmahalwy , response.data = camelizeKeys(response.data) |
woohooo! Thank you! |
Cannot do this in a transform:
The text was updated successfully, but these errors were encountered: