Version Packages - #1030
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This comment was marked as resolved.
This comment was marked as resolved.
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 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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@doc-kit/cli@1.0.1
Patch Changes
27a412a]:@doc-kit/core@1.0.1
Patch Changes
#1023
27a412aThanks @btea! - Fix empty paragraphs in API docs when a typed parameter list contains trailing non-parameter itemsWhen a loose markdown list in the API docs starts with typed parameters (e.g.
actual,expected,Returns) but also contains plain prose bullets (e.g. algorithm complexity notes), the entire list was previously treated as a parameter signature table. The non-parameter items had no name or type, causing them to render as empty<section>blocks on the built site.The fix splits the list at the first non-parameter item: typed items become the
FunctionSignaturetable, and the remaining items render as regular markdown content.Updated dependencies [
27a412a]:@node-core/doc-kit@2.0.1
Patch Changes
27a412a]:@node-core/doc-kit-legacy@1.0.1
Patch Changes
27a412a]:@doc-kit/generator-react@0.1.1
Patch Changes
#1023
27a412aThanks @btea! - Fix empty paragraphs in API docs when a typed parameter list contains trailing non-parameter itemsWhen a loose markdown list in the API docs starts with typed parameters (e.g.
actual,expected,Returns) but also contains plain prose bullets (e.g. algorithm complexity notes), the entire list was previously treated as a parameter signature table. The non-parameter items had no name or type, causing them to render as empty<section>blocks on the built site.The fix splits the list at the first non-parameter item: typed items become the
FunctionSignaturetable, and the remaining items render as regular markdown content.Updated dependencies [
27a412a]: