> The standard JSON encoder/decoder doesn't allow providing a naming strategy to automate the conversion
This is dangerous. You should be tagging all your fields even if the name matches exactly because, especially if inconsistently applied, someone might not realize that they are changing public schema with a refactor. If tags are completely missing in your codebase, you have to research every single type to determine if it gets serialized to JSON somewhere (good luck).
This is dangerous. You should be tagging all your fields even if the name matches exactly because, especially if inconsistently applied, someone might not realize that they are changing public schema with a refactor. If tags are completely missing in your codebase, you have to research every single type to determine if it gets serialized to JSON somewhere (good luck).
Avoiding magic is a feature.