It's such a small thing, but not having to explicitly instantiate embedded structs to specify embedded fields is going to clean up a lot of my DB code because we embed an Auditable structure to handle common fields like id, createdBy, etc. I've been looking forward to that for years! Generic functions are cool too I guess.
Do we need to add "/v2" behind every json import statement in every old codebase to future proof that shit or does plain encoding/json use the v2 systems under the hood? I understood that nothing should break with this version at least?
3 replies
Fina-fucken-leigh
It's such a small thing, but not having to explicitly instantiate embedded structs to specify embedded fields is going to clean up a lot of my DB code because we embed an Auditable structure to handle common fields like id, createdBy, etc. I've been looking forward to that for years! Generic functions are cool too I guess.
Do we need to add "/v2" behind every json import statement in every old codebase to future proof that shit or does plain encoding/json use the v2 systems under the hood? I understood that nothing should break with this version at least?