You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
After trying to fix this for a while this looks like it's just incompatible with our current ecosystem and would warrant a breaking change, my sincerest apologies for backtracking on this. I've added a test in the TS tests to avoid this in the future.
There's an inherent incompatibility with using the handleEvent interface as these types are also used by our consumers to type their events and components.
The reason will be displayed to describe this comment to others. Learn more.
Ah that's unfortunate, but I think it's for the best, and it isn't too late.
rschristian is working on prop and attr directives. This could be reintroduced with a directive as well. As a bonus, that will be visually consistent with solid, and unlock #428.
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.
Resolves #4581
Reverts #4538
After trying to fix this for a while this looks like it's just incompatible with our current ecosystem and would warrant a breaking change, my sincerest apologies for backtracking on this. I've added a test in the TS tests to avoid this in the future.
There's an inherent incompatibility with using the
handleEvent
interface as these types are also used by our consumers to type their events and components.