-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change most headers to be about module features #797
Conversation
Some headers could not be made about module features, and that's a strong signal that those sections should be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the cleanup. Let's get all of this out the door finally!
@@ -587,7 +585,7 @@ Make the following changes to `marker.nix`: | |||
+ }; | |||
``` | |||
|
|||
## Setting Option Values Within Other Modules | |||
## Defining Options in Other Modules |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be the "old" nomenclature that trips people up. In think we should leave that as it was.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah so
## Defining Options in Other Modules | |
## Declaring Options in Other Modules |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we're not declaring options in this section. But the first paragraph probably probably needs work.
Co-authored-by: Valentin Gagarin <[email protected]>
* Draft module system introduction tutorial * add intro/conclusion, rework prose, follow styleguide, clean diffs * Review pass * Apply suggestions from code review * fix whitespace * add some more motivation the each section * make scripts downloadable * address review comments * make script actually work ...hopefully. can't test it without Google API key * add file watching yes, this looks scary, and yes, it works. * update diff and wording * more notes on potential pitfalls * be explicit which `map` we mean * split nullable from default values * also wrap the geocode script * work through the tutorial to the end * add tutorial overview * `lib` is always passed * add separate section for `evalModules` and fix link * make option strucutre more self-explanatory * explain command line invocations * add note on incomplete reference documentation * add more highlight to the `config` distinction * fix parameter passing to the `./map` script * fix typo * fix wording * link to summer of nix * add missing word * link to Google Maps API docs * more explicit requirement * use correct module system terminology * Update source/tutorials/module-system/module-system.md * Apply suggestions from code review * whitespace * module-system.md: replace comments with captions * add missing lang for code-block * Update module system title * change most headers to be about module features (#797) * change most headers to be about module features Some headers could not be made about module features, and that's a strong signal that those sections should be removed. * Apply suggestions from code review * module-system.md: Fix header casing Co-authored-by: Alexander Groleau <[email protected]> Co-authored-by: asymmetric <[email protected]> Co-authored-by: Valentin Gagarin <[email protected]>
Some headers could not be made about module features, and that's a strong signal that those sections should be removed, IMO.