It would be cool that once data contracts are in place to provide interactive swagger docs that are dynamically built from each available entity in the org/repo. For example, if an ads/ads.schema.json file was created than a swagger doc would be available that outlines the model at the explicit end-point foe the org/repo ie. /org/repo/ads.
One golang tool I cam across to do this but doesn't necessarily need to be golang. Doesn't even necessarily need to be part of same lambda. Probably makes sense to keep it separate since and look into options for static deployment driven by js to avoid lambda and easily host ui for interactive docs on github repos.
This could be motivation to continue dev on spearhead docs. The docs websites could be spearhead docs. Spearhead docs would need customization to support interactive docs created from each databases schema. I think that would be worth considering.
Note this will require upgrade to ng 16 since hydration will be critical to maintaining low carbon website. Where as currently JavaScript is disabled/stripped for the demo spearhead docs deployments.
Begin putting together a strategy to take a contract schema and turn it into a quell panel page form. High level this will require creation of a solution that can automate panel pages from either json schemas directly and/or OpenAPI3 configuration. The OpenAPI3 option would require converting the json schema to the OpenAPI3 spec.
Curious whether a testing suite like TestCafe, Playright could be used as part for a Github action that would create the panel page form using a headless chrome browser. This would also double as an implicit end-to-end, regression test. Two birds one stone.
It would be cool that once data contracts are in place to provide interactive swagger docs that are dynamically built from each available entity in the org/repo. For example, if an ads/ads.schema.json file was created than a swagger doc would be available that outlines the model at the explicit end-point foe the org/repo ie. /org/repo/ads.
One golang tool I cam across to do this but doesn't necessarily need to be golang. Doesn't even necessarily need to be part of same lambda. Probably makes sense to keep it separate since and look into options for static deployment driven by js to avoid lambda and easily host ui for interactive docs on github repos.
serverless docs: https://www.serverless.com/plugins/serverless-openapi-documentation golang: https://goswagger.io/
This could be motivation to continue dev on spearhead docs. The docs websites could be spearhead docs. Spearhead docs would need customization to support interactive docs created from each databases schema. I think that would be worth considering.
https://spearhead-docs.carbonfreed.app/introduction
Begin putting together a strategy to take a contract schema and turn it into a quell panel page form. High level this will require creation of a solution that can automate panel pages from either json schemas directly and/or OpenAPI3 configuration. The OpenAPI3 option would require converting the json schema to the OpenAPI3 spec.
Curious whether a testing suite like TestCafe, Playright could be used as part for a Github action that would create the panel page form using a headless chrome browser. This would also double as an implicit end-to-end, regression test. Two birds one stone.