Add a DataType property on CompiledBindingExtension to enable specifying the start type explicitly on a binding. #7248
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing the start type explicitly on a binding. Fixes AvaloniaUI#6158
kekekeks
approved these changes
Dec 22, 2021
danwalmsley
pushed a commit
that referenced
this pull request
Jan 24, 2022
…n-binding Add a DataType property on CompiledBindingExtension to enable specifying the start type explicitly on a binding.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does the pull request do?
This PR adds a
DataTypeproperty to theCompiledBindingExtensiontype to allow people to specify the starting data type for a compiled binding directly on the binding object itself.What is the current behavior?
The binding start type is always inferred from the surrounding data context.
What is the updated/expected behavior with this PR?
Users can override the starting type for scenarios where the implicit inference is wrong.
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues
Fixes #6158