-
Notifications
You must be signed in to change notification settings - Fork 77
Normalize namespaces #1422
Normalize namespaces #1422
Conversation
@@ -1,4 +1,4 @@ | |||
namespace FSharpVSPowerTools | |||
namespace FSharp.Editing.VisualStudio.Coloring.UnusedSymbols |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why sub-namespace UunsedSymbols? Could we remove that for consistency with others?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Several types names clash with ones from SymbolClassifier.fs
since the implementations of normal and unused symbol classifiers are similar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, then it makes sense as is.
You've gotta normalize namespaces on all |
@dungpa regarding XAML (which I don't know anything of) any clue if Resharper would catch that as error? I can give a look at what Resharper says. |
I'm not sure ReSharper works on XAML files in F# projects. You could give it a try. |
From what I've seen, you'll have to hand-edit the xaml files to fix the On Thu, Jul 14, 2016 at 2:08 PM, Anh-Dung Phan notifications@github.com
|
Resharper at the rescue, it picks (at least the assembly) errors up. @vasily-kirichenko do you want me to make a PR on your branch? |
Yes, and if you remove the entire xmlns line, then go to the first error, On Thu, Jul 14, 2016 at 3:02 PM, Gauthier Segay notifications@github.com
|
It's ready. |
Great. Thanks. |
WIP