Releases: meshcloud/notion-markdown-cms
Release list
v0.11.1
What's Changed
- feat: implement support for block children paging by @JohannesRudolph in #7
Full Changelog: v0.11.0...v0.11.1
Contributors
Assets 2
v0.11.0
What's Changed
- feat: support bookmark block by @dewkul in #6
- feat: support paging for databases with more than 100 pages
New Contributors
Full Changelog: v0.10.1...v0.11.0
Contributors
Assets 2
v0.10.1
fix: do not concatenate rich text blocks with an extra space " " character in between. This fixes an issue with code blocks split into multiple rich text blocks
v0.10.0
render links as relative paths
We previously rendered all page links as absolute paths e.g.
/page.md. This created some problems
- some page generators that use base path prefixes like
/docs/page.md
and thus need to rewrite these links, which is brittle - text editors like VSCode cannot follow the markdown links properly
because they think the links are absolute to the root/of the fs - tools like textlint-rule-no-dead-link expect relative links to resolve
them correctly
Now rendering them as relative paths.
As part of these changes it was also necessary to switch properties
parsing to render properties only as plaintext, not markdown. This is
fine because we consider frontmatter to be data (YML), not markup. Most
site generators cannot deal with markdown in frontmatter anyway.
This change was necessary because we need to parse page properties
before we can determine the destination path of the markdown file where
the page will be rendered to, and that would now require resolving
relative links.
v0.9.0
This is a breaking change.
Redesigned properties handling
Consumers needed more control on how to emit frontmatter properties
for advanced scenarios such as renaming/remapping properties to match
the static site generator of choice. By taking this out of configuration
and instead supplying actual functions we can easily pass that control
to consumer while simultaneously removing a lot of complexity from
notion-markdown-sync itself (i.e. the notion of property-keys vs.
property-names). This simplifies the code overall.
v0.8.1
v0.8.0
- added notion api retries
- fix formatted whitespace rendering (e.g.
** **)