Update dependency vitepress-sidebar to v1.39.0 - #23
Merged
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
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 contains the following updates:
1.38.0→1.39.0Release Notes
jooy2/vitepress-sidebar (vitepress-sidebar)
v1.39.0Compare Source
useTitleFromFileHeadingno longer reads a comment written inside the frontmatter as the heading of a page. A comment starts with#, exactly like anh1does, so a line such as# https://vitepress.dev/reference/default-theme-home-pageleft at the top of a frontmatter became the title of the item. The frontmatter block is now removed before the content is read for a heading, and a file that holds no heading below it falls back to its file name, as it already did. The block is located by its delimiters, the way VitePress locates it, so it is removed even when what it holds is not valid YAML. (#223)sortMenusByFrontmatterOrdernow compares theorderof the frontmatter as a number instead of as text, so a negative or a decimal value is placed where its value belongs.-2no longer comes after-1, and2.25no longer comes after2.5. The sorting relied on thenumericoption ofIntl.Collator, which is a natural sort of the digit runs inside a string and reads neither a leading-as a sign nor a.as a decimal point, so it only agreed with numeric order for small positive integers. Sorting by a file name or a title is unaffected, as it is still the natural sort that is wanted there. Anorderthat does not read as a number now falls back tofrontmatterOrderDefaultValue, as the documentation describes, instead of being sorted asNaN. (#233)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.