GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||
GeezerVison is showing github.com — Clean up MshObject.cs and MshMemberInfo.cs by daxian-dbw · Pull Request #7446 · PowerShell/PowerShell Conversation
|
|
Looks great! Ship it! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
2cd7fb3 to
402b90a
Compare
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I marked not all issues (one per type).
I absolutely don't agree use new pattern ( => ) in one file. If we want use this we should fix all code base.
In typical PR we modify some files and if the files have different style this is a difficulty for contributor.
I would like us to use the same styles and formatting throughout the code. These will greatly improve code manageability.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Did we say about out TypeTabel typeTable?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
That it was less noisy and repetitive?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
How many delegate () {} patterns we have in our code? I unlike use new pattern in one place and add a chaos. I'd prefer use the same pattern in all code and if we want new pattern I'd expect that we fix all code in one PR.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I think we should write new code using new patterns. If someone wants to clean up older code, fine. But I would really dislike having to use some old construct just because some other old code hasn't been updated.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Why last arguments is on one line? And why we don't use named arguments for constants?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I unlike use new pattern in one file and add a chaos. I'd prefer use the same pattern in all code and if we want new pattern I'd expect that we fix all code.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I like using new patterns in new code. I don't in any way feel that it in any way creates chaos. We must have completely different ways of using that word.
If you get to a file using the older pattern, you recognize it as older code, but we are capable of reading and understanding both versions.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Extra space after (XmlNode).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should we use spaces? { this.instance }
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
The same.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Why this is on new line?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Extra space.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Extra space.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I think we should write new code using new patterns. If someone wants to clean up older code, fine. But I would really dislike having to use some old construct just because some other old code hasn't been updated.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I like using new patterns in new code. I don't in any way feel that it in any way creates chaos. We must have completely different ways of using that word.
If you get to a file using the older pattern, you recognize it as older code, but we are capable of reading and understanding both versions.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Dongbo Wang (@daxian-dbw) Can you resolve conflicts? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
402b90a to
dd79054
Compare
|
The PR has been rebased. Ilya (@iSazonov) maintainers can push changes to PRs, so please feel free to address the issues that are brought up in your comments. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Steve Lee (@SteveL-MSFT) Dongbo Wang (@daxian-dbw) New commits was added. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Looks like we just need to resolve the merge conflict |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
The code needs to be rebased to fix the test issue on linux as well |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
27394ee to
8061354
Compare
|
Rebased. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
CI Appveyor temporary failed. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Clean up style issues.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.