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
Each component on the components page should link to a detailed page with more information, mainly how to configure it and documentation for all of the fields.
One open question is how we'll know which config object each service uses. We could scrape it based on the imports, but it will be fairly brittle. We may want some way in the clutchdoc or otherwise for a service to declare its config type.
We have some proto documentation capabilities in the docs generator that can list out the object. We'll need to add onto this a bit to scrape comments, etc if we really want to make this effective.
Complexity [S/M/L]: M
The text was updated successfully, but these errors were encountered:
Description
Each component on the components page should link to a detailed page with more information, mainly how to configure it and documentation for all of the fields.
One open question is how we'll know which config object each service uses. We could scrape it based on the imports, but it will be fairly brittle. We may want some way in the
clutchdoc
or otherwise for a service to declare its config type.We have some proto documentation capabilities in the docs generator that can list out the object. We'll need to add onto this a bit to scrape comments, etc if we really want to make this effective.
Complexity [S/M/L]: M
The text was updated successfully, but these errors were encountered: