Remove unused usings #299
Merged
Remove unused usings #299
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
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.
I had a go at building against the latest Avalonia nightly to try testing with it, and got a bunch of build failures due to Avalonia API changes, but also a few due to unresolved namespace uses that in some cases turn out not be be needed (e.g. the latest Avalonia has removed the reference to JetBrains.Annotations, and it looks like AvaloniaEdit contains some
using JetBrains.Annotationsbut doesn't actually use the attributes, so removing them avoids a build break).I then just went and ran the VS code tidy on the project to remove all the unused usings rather than just those, and this is the result in case anyone is interested.