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
I find it super confusing to have to edit code in one of the /_docs-sources or /docs folders, wait for the code to be generated locally, and then commit both. A more natural workflow would be we edit one of those folders, and do the git commit. Then when the docs site update is published, it generates the right code.
If we want to validate that it does in fact build correctly before we commit the release, then we should probably bake that in as an automated test to validate the build rather than a user workflow.
Plus, consider if users want to contribute to docs. Having to ramp up on two different folders will be all the more confusing.
The text was updated successfully, but these errors were encountered:
I find it super confusing to have to edit code in one of the
/_docs-sources
or/docs
folders, wait for the code to be generated locally, and then commit both. A more natural workflow would be we edit one of those folders, and do the git commit. Then when the docs site update is published, it generates the right code.If we want to validate that it does in fact build correctly before we commit the release, then we should probably bake that in as an automated test to validate the build rather than a user workflow.
Plus, consider if users want to contribute to docs. Having to ramp up on two different folders will be all the more confusing.
The text was updated successfully, but these errors were encountered: