docs: update cvars list and generator #174
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
merge this last, i will regenerate with the changes from other prs |
also add pipe escape, path fallback, cvar filter, and EOF LF to cvars.js also add contribution tutorial for generator TODO: should cvars.js be in docs? to make it more obvious what it's for
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
cvars.js- cvar description pipe escape, path fallback to cwd, filter out custom (sar_alias/sar_function) and internal (_sar_svar_capture_stop) cvars, and add EOF LF in generated filedocs/cvars.md- regendocs/contributing.md- add contrib tutorial for cvars.jssrc/Features/Hud/Hud.cpp- fixsar_hud_fpshelpstr to match docs (I still don't see why this HUD exists though)Should
cvars.jsbe indocs? To make it more obvious what it's for