**Geoff #PID<0.57.0>** @cooler_ranch · May 14, 2018, 00:48

**Geoff #PID<0.57.0>** @cooler_ranch · May 14, 2018, 00:48

Geoff #PID<0.57.0> @cooler_ranch

May 14, 2018, 00:48

#elixir question Show more

It's really frustrating to use JSON from the outside world using string-based keys in camelCase. Elixir libraries can make these JSON objects into maps really easily, but the keys remain strings and in camelCase instead of the preferred snake_case.

Would anyone think it worthwhile to have a few functions that will take a map with camelCase, string keys and return the same map but with atom keys and in snake_case?

**Geoff #PID<0.57.0>** @cooler_ranch · May 14, 2018, 00:54

**Geoff #PID<0.57.0>** @cooler_ranch · May 14, 2018, 00:54

May 14, 2018, 00:54

Geoff #PID<0.57.0> @cooler_ranch

#elixir question Show more

pros:
- Lower memory use if you have many processes with commonly repeated keys.
- Keep keys in elixir style, while not forcing it into the larger world.

cons:
- This amount of work might be unnecessary for some use-cases (where memory isn't an issue, but extra computation could be undesirable or prohibitive to larger goals)
- O(n) operations add up with more keys/nesting

caveats: using String.to_existing_atom/1 so we don't grow the atom table so large it crashes the VM 🙃

**Geoff #PID<0.57.0>** @cooler_ranch · 2018-05-14T00:59:25Z

Geoff #PID<0.57.0> @cooler_ranch

#elixir question Show more

I've got it pretty much done in a small module, but I'm not sure if this is Actually Useful to others, or if I'm just scratching an itch and doing an exercise.

Seems silly to publish ~100 lines of code as a library, especially when there are a lot of toy libraries cluttering Hex.pm. But if people like the idea, I can break it out into its own library and publish.

#elixir

May 14, 2018, 00:59 · Web · 1 · 0