Currently when a new field is needed to be added to the context, the author must add the field many times which is not a great experience. Further, the current examples folder serves two purposes: testing and examples. When the SDKs run its testing processes, it will utilize the examples folder to ensure things are generated correctly. This makes adding useful examples for end users more difficult as it needs to adhere to a strict format.
So with these two issues, I believe we can introduce code gen'ing to better the experience of authors and end users who are interested in looking at examples.
Add a tool to code gen schemas
Use the same tool to generate examples
Add a new testing folder for the purpose of tests
Generate test payloads using the same code gen'ing tool
A proposal will need to be written to outline what the new directory structure will look like and any new tool that needs to be added.
Currently when a new field is needed to be added to the context, the author must add the field many times which is not a great experience. Further, the current examples folder serves two purposes: testing and examples. When the SDKs run its testing processes, it will utilize the examples folder to ensure things are generated correctly. This makes adding useful examples for end users more difficult as it needs to adhere to a strict format.
So with these two issues, I believe we can introduce code gen'ing to better the experience of authors and end users who are interested in looking at examples.
A proposal will need to be written to outline what the new directory structure will look like and any new tool that needs to be added.