chore(v3.0.0-release): release of new generation of plugin #74
Conversation
This file contains 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
… default This means that now plugin forever remembers what are initial extenstions and views were registered and stored in the Obsidian Vault.
…es default extensions
…ry, not just plugin's settings
… toggle in the settings Now, when "Silence errors" mode is enabled, errors will be debugged in the console and no notifications would appear. Fix of #70
… script and little refactoring of them
…upport files with commas and empty strings
…s, feature fix of #63 Now plugin supports and will support (at future moment older versions) older versions and try to convert/adapt them in new format/config and saving old data. May be unstable, but allows user to easy update plugin without headaches.
2 tasks
This was
linked to
issues
Oct 2, 2024
… for UNIX-systems
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.
PRs: global update, moving to the next generation of plugin
Before writing anything about your changes in this PR, checklist this items:
By agreeding and following this project's documentation, you are reminded that your's commit and styling of changes must follow this project's documentation, in case of “de-followization”, there are two ways before you make sure to publishing your PR:
For amending old commit, see the stackoverflow question1, more about changing commits in official docs for github:
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message/
Changes with that PR
Please, write below every changes you made:
Check future changelogs and release page: update is too big to write it here.
Process of testing for that PR
answer (y/n): (y);
Hard-testing: meaning developer imitated UX with plugin.
Additional context for that PR
...
Footnotes
https://stackoverflow.com/questions/17338792/amending-old-commit/ ↩