Releases: rasendubi/uniorg
[email protected]
Major Changes
-
#123
2cb1965
Thanks @rasendubi! - Fix list item paragraph handling to match ox-html's behavior: strip paragraphs from list items when they are the only child or followed by at most one sub-list.While this is technically a fix to match the expected behavior, it's marked as a major change to highlight that it alters the HTML output. If you depend on the previous HTML structure, you'll need to review and update any CSS or JavaScript that assumes the old output.
[email protected]
Minor Changes
-
#130
381b67c
Thanks @rasendubi! - Add position tracking to nodes according to the unist spec.Each node will include a position field with start and end points containing line, column, and offset information when enabled. Position tracking is disabled by default to avoid processing overhead. You can enable it by setting
trackPosition: true
in parser options. -
#131
da9d596
Thanks @rasendubi! - Add support for passing parser options to the unified plugin.Previously, you couldn't configure the parser through the unified plugin API. Now you can pass options when using the plugin:
unified().use(uniorgParse, { todoKeywords: ['TODO', 'DONE', 'WAITING'] })
and these options will be passed to the parser.
[email protected]
Major Changes
-
#126
7531419
Thanks @rasendubi! - Move uniorg-parse and uniorg-rehype into peer dependencies.This is done to give you precise control over your versions of uniorg-parse and uniorg-rehype, so you can account for any quirks or specific needs.
This shall also allow us to maintain core uniorg packages and integrations independently, so you will be able to use newer integration packages with having to upgrade the parser or vice versa.
This is a breaking change because you now need to explicitly install uniorg-parse and uniorg-rehype as dependencies in your projects. Previously, these were included as direct dependencies of the packages.
Patch Changes
- Updated dependencies [
7531419
]:- @uniorgjs/[email protected]
[email protected]
Major Changes
-
#126
7531419
Thanks @rasendubi! - Move uniorg-parse and uniorg-rehype into peer dependencies.This is done to give you precise control over your versions of uniorg-parse and uniorg-rehype, so you can account for any quirks or specific needs.
This shall also allow us to maintain core uniorg packages and integrations independently, so you will be able to use newer integration packages with having to upgrade the parser or vice versa.
This is a breaking change because you now need to explicitly install uniorg-parse and uniorg-rehype as dependencies in your projects. Previously, these were included as direct dependencies of the packages.
Patch Changes
- Updated dependencies [
7531419
]:
@uniorgjs/[email protected]
Major Changes
-
#126
7531419
Thanks @rasendubi! - Move uniorg-parse and uniorg-rehype into peer dependencies.This is done to give you precise control over your versions of uniorg-parse and uniorg-rehype, so you can account for any quirks or specific needs.
This shall also allow us to maintain core uniorg packages and integrations independently, so you will be able to use newer integration packages with having to upgrade the parser or vice versa.
This is a breaking change because you now need to explicitly install uniorg-parse and uniorg-rehype as dependencies in your projects. Previously, these were included as direct dependencies of the packages.
[email protected]
Major Changes
-
#121
12d0768
Thanks @rasendubi! - Breaking change: Updated to support Astro 5.x (no longer compatible with Astro 4.x or earlier).If you're upgrading, make sure you've upgraded Astro to version 5.x
[email protected]
[email protected]
Patch Changes
- Updated dependencies []:
- @uniorgjs/[email protected]
@uniorgjs/[email protected]
Patch Changes
- Updated dependencies [
ebc6ab0
]:
[email protected]
Minor Changes
-
#109
dbf6452
Thanks @rasendubi! - Supportexport-snippet
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.export-snippet
has the following form:@@backend:value@@
. Example:@@html:<b>@@some text@@html:</b>
.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
-
#111
b45baf9
Thanks @rasendubi! - Supportline-break
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.