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
Describe the bug Throw Exception "Ambiguous match found" when navigate into property Parent.
To Reproduce Steps to reproduce the behavior:
Expected behavior navigate to Parent property without throw Exception .
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Throw Exception is there
Avalonia/src/Avalonia.Diagnostics/Diagnostics/ViewModels/ControlDetailsViewModel.cs
Line 407 in 9eb18b2
the reason is because Parent property is declared several times with different return type in same hierarchy .
Avalonia/src/Avalonia.Controls/Control.cs
Line 121 in 9eb18b2
Avalonia/src/Avalonia.Styling/StyledElement.cs
Line 269 in 9eb18b2
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
Throw Exception "Ambiguous match found" when navigate into property Parent.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
navigate to Parent property without throw Exception .
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Throw Exception is there
Avalonia/src/Avalonia.Diagnostics/Diagnostics/ViewModels/ControlDetailsViewModel.cs
Line 407 in 9eb18b2
the reason is because Parent property is declared several times with different return type in same hierarchy .
Avalonia/src/Avalonia.Controls/Control.cs
Line 121 in 9eb18b2
Avalonia/src/Avalonia.Styling/StyledElement.cs
Line 269 in 9eb18b2
The text was updated successfully, but these errors were encountered: