We too do lots of code generation, but I have the opposite experience.

The articles example would imply in our use case:

1) add one key to the schema (which is database independent), which will generate encoders, decoders, apis (to work with the data structure, not in network-sense) automatically

2) add the key in the views you want to add it (when updating/reading or more complex network apis)

3) specify how the key is retrieved/saved in the use cases (controller-like)

4) use the key in the frontend.

It took me longer to write this post from mobile than it would've taken me do the first 3 steps.