-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typescript JSDoc Part 2 - Export custom component types #5141
Draft
awikkerink
wants to merge
21
commits into
main
Choose a base branch
from
awikkerink/typescript-add-type-exports
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+128
−2
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
Thanks for the PR! 🎉 We've deployed an automatic preview for this PR - you can see your changes here:
Note The build needs to finish before your changes are deployed. |
* Only export the type for typescript/jsdoc
awikkerink
force-pushed
the
awikkerink/typescript-add-type-exports
branch
from
November 13, 2024 15:42
2c26bf1
to
001cf6f
Compare
2 tasks
awikkerink
changed the title
Export custom component types
HTMLElementTagNameMap Part 3 - Export custom component types
Dec 3, 2024
awikkerink
changed the title
HTMLElementTagNameMap Part 3 - Export custom component types
Typescript JSDoc Part 3 - Export custom component types
Jan 3, 2025
awikkerink
changed the title
Typescript JSDoc Part 3 - Export custom component types
Typescript JSDoc Part 2 - Export custom component types
Jan 3, 2025
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.
This step is pretty easy to automate. The tricky part is when too many typedefs are added. A better approach would be to export all of the component types, since it's possible to get the class via
customElements.get
Can be merged before Parts 1 and 2, since this is just additive. Merging this first would just change the generated mapping.d.ts