camelize keys about apisauce

[mmahalwy]

The way I am getting around this is:

api.addResponseTransform(response => {
    if (response.data) {
      const data = camelizeKeys(response.data);

      Object.keys(response.data).forEach(key => {
        delete response.data[key];
      });

      Object.keys(data).forEach(key => response.data[key] = data[key]);
    }
  });

It's not elegant at all. Seems like I cannot change response.data by assigning a new object. I can only change keys and values.

[skellock]

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 config).

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.

[mmahalwy]

@skellock makes sense. What do you suggest is the best way then? My solution works for now, but it's... not great.

[skellock]

Ok @mmahalwy , [email protected] is now out. Reassigning data (and everything else) is now a thing.

response.data = camelizeKeys(response.data)

[mmahalwy]

woohooo! Thank you!