-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resharper compatibility #13
Comments
Hi, arteny! I'm surprised for such problem with resharper. Some workaround for this doesn't exists yet, but I think it will be possible to add for operator '!' alias 'not' like it was made for '&&' and '||' operators. In principle, it is quick to do and write tests. In the near future I will do it. So, for examle, your xaml code will be:
Just do not forget to comment on the issues you have already created |
Thank you for kind support! |
version 2.2.3.0 with that feature is released |
It doesn't solve this issue. If change ! for not, Resharper error message changed to: |
And it is not related "complex" field, but anyone:
or
|
Arteny, unfortunately I don't use Resharper, so as I undestand from your issue description, Resharper doesn't like special symbol '!' and that is the reason of error. Therefore I have added operator 'not' in a hope that resharper will not show error. As I know resharper can't affect on compilation process, so even if you have that "resharper error" you can still compile and launch your project. Can you just turn off messages about these kinds of errors in resharper options? If you other good solutions, please write about it. |
Seems I found workaround, it is necessary to include path to single quotes like
|
And resharper don't show error? |
yes, it is |
Such 'complex' property access shown as error in Resharper:
<Setter Property="IsEnabled" Value="{c:Binding !DataContext.IsRemoved}"/>
! pointed as not expected token.
And I can not ignore this line something like
<!-- ReSharper disable Xaml.BindingWithContextNotResolved -->
Only was is Disable Resharper Daemon for all file, but i don't like it much.
Is there some workaround?
The text was updated successfully, but these errors were encountered: