feat: added type definitions and textarea component #87
Conversation
This file contains hidden or 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
pixelmund
changed the title
|
@pixelmund thanks for the PR! What made you close it? Would be much appreciated if you submitted this (although I'd ask that you submit the TS definitions in a different PR from the textarea) EDIT: I've added a PR for the textarea component here, along with adding test configs for components: #88 |
|
I will reopen it later today with the type definitions only. |
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.
Those are the type definitions for svelte-forms-lib, there might be some optimizations but it's a good starting point.
Svelte currently does not support generics in components, there are some discussions around it but i couldn't find a solution.
Also i have added the textarea helper component as requested here: #86
fixes #34
fixes #81
implements #86