We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have hidden XAML errors in #203, but now it's problematic to figure out what are the real errors (e.g. see #259).
I propose let's do two things:
The text was updated successfully, but these errors were encountered:
This would be a great fix. If there's an issue in the ViewModel it's very difficult to find it.
Sorry, something went wrong.
ForNeVeR
No branches or pull requests
We have hidden XAML errors in #203, but now it's problematic to figure out what are the real errors (e.g. see #259).
I propose let's do two things:
The text was updated successfully, but these errors were encountered: