Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding support to Markdown Cartridges #15

Merged
merged 8 commits into from
Jan 11, 2024
Merged

Adding support to Markdown Cartridges #15

merged 8 commits into from
Jan 11, 2024

Conversation

icebaker
Copy link
Owner

@icebaker icebaker commented Jan 9, 2024

News in this version:

Adopting Nano Bots Specification 3.0.0

Breaking changes:

  • Cartridges must have a .yml or .yaml extension.
  • NANO_BOTS_STATE_DIRECTORY has been renamed to NANO_BOTS_STATE_PATH.
  • NANO_BOTS_CARTRIDGES_DIRECTORY has been renamed to NANO_BOTS_CARTRIDGES_PATH.

Additionally, NANO_BOTS_STATE_PATH now supports multiple paths. These paths follow the Linux convention of being separated by a colon :. For example, you can specify NANO_BOTS_STATE_PATH like this: /home/user/cartridges-a:/home/user/cartridges-b.

All of these changes were made to be backward compatible, so people using the old NANO_BOTS_STATE_DIRECTORY or NANO_BOTS_CARTRIDGES_DIRECTORY will not face issues.

Experimental:

Cartridges can now be written in Markdown for an improved writing experience in apps like Obsidian.

This is a valid cartridge that will be correctly interpreted. Internally, implementations should extract the code blocks, consolidate them, and ignore the rest of the content:

cartridge

The following extensions will be supported for markdown cartridges: md mkdn mdown markdown

@icebaker icebaker changed the title adding support to markdown cartridges Adding support to Markdown Cartridges Jan 10, 2024
@icebaker icebaker merged commit 50677c9 into main Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant