You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During our 1:1 today, @tkporter and I talked about the new config format and possible ways to document it. Ultimately it would be nice to have some sort of markdown config that we can point people at if not even a config that is automatically inserted into our gitdocs. A first step to either of those is to have some sort of markdown-from-schema conversion.
During our 1:1 today, @tkporter and I talked about the new config format and possible ways to document it. Ultimately it would be nice to have some sort of markdown config that we can point people at if not even a config that is automatically inserted into our gitdocs. A first step to either of those is to have some sort of markdown-from-schema conversion.
A solution that I can see after very little searching would be to use zod-to-json-schema and then jsonschema2md.
There's also a typedoc-plugin-zod that might work.
The problem this answers is:
As a hyperlane operator, I want to have an easy reference of what the current configuration shape looks like.
Relates to #2215
The text was updated successfully, but these errors were encountered: