Some pre-processing is done on RetroAchievements' API response, inspired by the JS library, such as renaming variables, converting 1/0 to true/false, etc...
However, maintaining this pre-processing to match the JS responses is very time consuming, and confusing for any end user using the raw API.
It's easier to simply avoid doing and pre-processing, simplifying the RetroAchievements.Raw methods. And such breaking changes are better before a release is made.
Some pre-processing is done on RetroAchievements' API response, inspired by the JS library, such as renaming variables, converting
1/0totrue/false, etc...However, maintaining this pre-processing to match the JS responses is very time consuming, and confusing for any end user using the raw API.
It's easier to simply avoid doing and pre-processing, simplifying the
RetroAchievements.Rawmethods. And such breaking changes are better before a release is made.