type safety? #6
Open
type safety? #6
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
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.
I'm guessing this project is a bit dead ;)
I saw WiredElements and thought it looked just so cute, I had to use it :)
Realized a bit too late what I got myself into...
The landscape for React & WebComponents is better in 2023, but the experience isn't a smooth ride either (yet?).
Anyway, I pushed through, and this PR is an example of some additional work that needs to be done to make the components fully usable in a TypeScript project. (ie so you don't have to use
(event.target as any).value as stringwhen using the onChange event.So, this PR to test the waters, see if there is interest in making this project move forward :)