Perf: Exclude the unnecessary fields defined on a specific version #1202
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
… field in .NET 8 or higher
github-actions
bot
added
controls
pomianowski
approved these changes
Oct 24, 2024
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.
Exclude the definition of the
CanCenterOverWPFOwnerPropertyInfofield in .NET 8.0 or higherPull request type
Please check the type of change your PR introduces:
What is the current behavior?
In the current implementation, even if the
CanCenterOverWPFOwnerPropertyInfofield is not used (.NET 8 and higher), this field is still being initialized.Issue Number: N/A
What is the new behavior?
Exclude the definition of the
CanCenterOverWPFOwnerPropertyInfofield in .NET 8.0 or higher