c79334ffbb
## Summary of the Pull Request This creates an `elevated-state.json` that lives in `%LOCALAPPDATA%` next to `state.json`, that's only writable when elevated. It doesn't _use_ this file for anything, it just puts the framework down for use later. It's _just like `ApplicationState`_. We'll use it the same way. It's readable when unelevated, which is nice, but not writable. If you're dumb and try to write to the file when unelevated, it'll just silently do nothing. If we try opening the file and find out the permissions are different, we'll _blow the file away entirely_. This is to prevent someone from renaming the original file (which they can do unelevated), then slapping a new file that's writable by them down in it's place. ## References * We're going to use this in #11096, but these PRs need to be broken up. ## PR Checklist * [x] Closes nothing * [x] I work here * [x] Tests added/passed * [ ] Requires documentation to be updated - maybe? not sure we have docs on `state.json` at all yet ## Validation Steps Performed I've played with this much more in `dev/migrie/f/non-terminal-content-elevation-warning` ###### followed by #11308, #11310 |
||
|---|---|---|
| .. | ||
| allow.txt | ||
| apis.txt | ||
| chinese.txt | ||
| colors.txt | ||
| fonts.txt | ||
| japanese.txt | ||
| math.txt | ||
| microsoft.txt | ||
| names.txt | ||
| README.md | ||
Allow files are lists of words to accept unconditionally
While check spelling will complain about an expected word which is no longer present, you can include things here even if they are not otherwise present in the repository.
E.g., you could include a list of system APIs here, or potential contributors (so that if a future commit includes their name, it'll be accepted).
Files
| File | Description |
|---|---|
| Allow | Supplements to the dictionary |
| Chinese | Chinese words |
| Japanese | Japanese words |
| Microsoft | Microsoft brand items |
| Fonts | Font names |
| Names | Names of people |
| Colors | Names of color |