Namespace, filename and property-name cleanups #55
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
|
@vany0114 This is the PR you can merge onto yours if you are happy. It's frustrating that the build sometimes fails the second build of a PR because of
we can try to have a look at that ... |
Merged
|
Thanks a lot @reisenberger!
Yeah, it's very annoying, I can create an issue if you want, just to have it on the radar. |
Opened #56 with some investigation. |
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.
XInternal, to avoid clashes with identically named methods. (If identically named, the compiler resolves the correct item (the method) when the correctusingstatement is in place; but gives messages about 'Cannot access internal property', which may be confusing for users, if theusingstatement is missing.)*Fault*files/classes to*Outcome*