Standardize Part1 #115 #121
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
|
bump!! |
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.
First words of pref number descriptions standardized: using:
enable, disable, set (& one case of reset), start (two of these), enforce, limit, hide, spoof, control
These include items with a prefix such as all of the 1600s:
/* 1603: CROSS ORIGIN: control when to send a referer [SETUP]
/* 1605: ALL: disable spoofing a referer
This now leaves 37 preferences not starting with those words, and some definitely need work. Will do in a Standardize Part2 PR
Also fixed up
[NOTE] Capitalize first letter..Also fixed up numbers
0 = blahto0=blahas per the bulk of them already had no spacingOther minor changes
Please review in case of any f**kups.