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
{{ message }}
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
When there is some kind of strange configuration in webpack, karma or typescript we sometimes add comments to explain why it is there. I think it would be nice if we would have a document where we explain our motivation behind all the configuration options.
I would like to create this document, but right now there is no separation between the boilerplate documentation (for the new module) and the readme for the boilerplate itself.
create configuration page
add description for each config file
link to configuration page from readme
The text was updated successfully, but these errors were encountered:
Agree with the solution, all documentation related with instructing, examples and demos should be in other section like wiki or even an external web site
Boilerplate info is now placed at the bottom of the readme (that's stripped of in the generator), but moving it to github wiki pages might be a better option.
Note, before removing the bottom part of the readme, we probably need to update the yeoman generator to make sure it doesn't break at the indexOf being -1 :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When there is some kind of strange configuration in webpack, karma or typescript we sometimes add comments to explain why it is there. I think it would be nice if we would have a document where we explain our motivation behind all the configuration options.
I would like to create this document, but right now there is no separation between the boilerplate documentation (for the new module) and the readme for the boilerplate itself.
The text was updated successfully, but these errors were encountered: