-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Fix TemplateBinding and allow custom attributes in XamlValueConverter #14612
Fix TemplateBinding and allow custom attributes in XamlValueConverter #14612
Conversation
You can test this PR using the following package version. |
…g-and-allow-attributes-in-XamlValueConverter # Conflicts: # src/Markup/Avalonia.Markup.Xaml.Loader/xamlil.github
You can test this PR using the following package version. |
…g-and-allow-attributes-in-XamlValueConverter # Conflicts: # src/Markup/Avalonia.Markup.Xaml.Loader/CompilerExtensions/Transformers/AvaloniaXamlIlTransformInstanceAttachedProperties.cs # src/Markup/Avalonia.Markup.Xaml.Loader/xamlil.github # src/tools/Avalonia.Generators/Compiler/RoslynTypeSystem.cs
…in-XamlValueConverter
…in-XamlValueConverter
… and fix ColorPicker usage
…in-XamlValueConverter
You can test this PR using the following package version. |
Depends on kekekeks/XamlX#105
What does the pull request do?
How was the solution implemented (if it's not obvious)?
Instead of hardcoding compiler for TemplateBinding support, I decided to go with a custom attribute usable by the compiler.
Unfortunately, using this attribute is rather complicated, as XamlX as for now didn't have IPropertyInfo alternative, so I had to implement it first on our backends. Following changes to XamlValueConverter and updating all places where it's used. Because of that PR is rather big, so I wouldn't expect it to be merged soon.
Checklist
Fixed issues
Fixes #14576
Fixes #2357