Fix For Attribute to use System.Attribute #250
Merged
Conversation
This file contains hidden or 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
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce?
fixes #246
What is the current behavior?
#246
What is the new behavior?
This pull request includes changes to improve code consistency and update the attribute definitions in the
ReactiveUI.SourceGeneratorsnamespace. The most important changes involve replacing direct references toAttributewith fully qualifiedglobal::System.Attributeand removing unusedusing System;directives across multiple files.Cleanup of unused directives:
using System;directives in auto-generated test files to reduce clutter and improve readability.Minor refactoring:
MyReactiveClassfield withViewModelin the constructor ofMyReactiveControlof the ReadMe to improve clarity.What might this PR break?
None expected
Please check if the PR fulfills these requirements
Other information: