-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Readability improvement and format changes #2810
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
Conversation
zadjii-msft
left a comment
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.
I'm blocking only on the "OS" thing, because that's actually important
doc/AddASetting.md
Outdated
| `.../console/published/wincon.w` in the OS repo when you submit the PR. | ||
| ### 1. Add to wincon.w | ||
| * THIS IS NOT IN OPENCONSOLE. Make sure you update | ||
| `.../console/published/wincon.w` in the Open Source repository when you submit the Pull Request. |
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.
Actually, this is supposed to be "OS". I'm referring to the actual Windows OS repo here, this isn't a change that can be made entirely in the open-source repo here.
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.
Oh, my mistake. I'll remember that.
I changed it; is that fine now or should it just be 'OS' (without 'repo')?
doc/AddASetting.md
Outdated
| - `propsheet/registry.cpp@GetRegistryValues` should make sure to read the property from the registry | ||
|
|
||
| 4. Add the field to the propslib registry map | ||
| ### 4. Add the field to the propslib registry map |
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.
Making these into h3's without any sub-points feels stylistically weird to me - @bitcrazed / @cinnamon-msft want to weigh in on this?
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.
@zadjii-msft I agree Mike; I did find it to be 'stylistically weird' as well, but then I thought it would be breaking the uniformity otherwise.
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.
I feel making them bold would be better than h3's
| - `Wtypes.PROPERTYKEY PKEY_Console_` | ||
| - `NT_CONSOLE_PROPS` | ||
| ### 7. Update the feature test properties to get add the setting as well | ||
| `ft_uia/Common/NativeMethods.cs@WinConP`: |
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.
This particular sub point seems weird now, it feels like it lost the connection to the parent bullet point (which is now the header)
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.
What do you suggest should be done?
Co-Authored-By: Mike Griese <migrie@microsoft.com>
Co-Authored-By: Mike Griese <migrie@microsoft.com>
zadjii-msft
left a comment
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.
Sorry for delays in reviewing. I think it's mostly fine, I just have a minor nit around the formatting in bullet point 7.
doc/AddASetting.md
Outdated
| **7. Update the feature test properties to get add the setting as well** | ||
| `ft_uia/Common/NativeMethods.cs@WinConP`: | ||
| - `Wtypes.PROPERTYKEY PKEY_Console_` | ||
| - `NT_CONSOLE_PROPS` |
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.
I think this needs to maybe all be indented another layer, like the src/propsheet/registry.cpp entries in bullet 3. Otherwise it runs into the title in the rendered markdown
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 problem with the delay, Mike.
I changed it now. Comments?
| **7. Update the feature test properties to get add the setting as well** | ||
| `ft_uia/Common/NativeMethods.cs@WinConP`: | ||
| - `Wtypes.PROPERTYKEY PKEY_Console_` | ||
| - `NT_CONSOLE_PROPS` |
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.
| - `NT_CONSOLE_PROPS` | |
| - `NT_CONSOLE_PROPS` |
(same here)
|
|
||
| **7. Update the feature test properties to get add the setting as well** | ||
| `ft_uia/Common/NativeMethods.cs@WinConP`: | ||
| - `Wtypes.PROPERTYKEY PKEY_Console_` |
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.
| - `Wtypes.PROPERTYKEY PKEY_Console_` | |
| - `Wtypes.PROPERTYKEY PKEY_Console_` |
We should probably keep the indentation of these sub-points consistent with other indentation in this file
| Now, your new setting should be stored, just like all the other properties. | ||
|
|
||
| **7. Update the feature test properties to get add the setting as well** | ||
| `ft_uia/Common/NativeMethods.cs@WinConP`: |
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.
| `ft_uia/Common/NativeMethods.cs@WinConP`: | |
| - `ft_uia/Common/NativeMethods.cs@WinConP`: |
Without the hyphen here, markdown will just concatenate this line with the previous line
|
This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
References
PR Checklist