{{ message }}
Repository navigation
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.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be cleaner/safer if this "property upgrade" happens as soon as possible (i.e. inside the strategy constructor). For example, this allows handling setting values via both properties and attributes to remain in sync. (As it is now, if a property is set before upgrading and then the corresponding attribute is set after upgrading (but before connecting), the property value will be used, despite the attribute being set later.)
This would require the element to be passed to the strategy constructor though, which might be a breaking change 😞
BTW, we should also ensure that the strategy is instantiated before using it in the input getters/setters, because it is not guaranteed to be.