Uh oh!
There was an error while loading. Please reload this page.
feat(types): expose MarkdownParsedContent for improved type generics - #1199
Merged
Conversation
|
| Name | Link |
|---|---|
| 🔨 Latest commit | 7ccec6e |
MarkdownParsedContent for improved markdown type genericsMarkdownParsedContent for improved type genericsTahul
commented
Jun 3, 2022
Contributor
This is an excellent first step towards #1057 ; would love to include you in the loop about this type generation feature! Thank you a lot @harlan-zw 😄 |
Tahul
approved these changes
Jun 3, 2022
harlan-zw
commented
Jun 4, 2022
ContributorAuthor
Yes please do @Tahul, I was thinking about how this could be achieved |
Merged
farnabaz pushed a commit
that referenced
this pull request
Sep 7, 2022
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
🔗 Linked issue
❓ Type of change
📚 Description
Add a Markdown specific parsed content schema, allowing end-users to build generics that have better type safety.
I did see #1057, I'd presume we'd need a safer type for markdown files when that's built so this should help with that.
📝 Checklist