Open
Conversation
Owner
|
LGTM, thank you for the contribution! I think it would be good to include the snacks toggle example in the README. Can you add that as well? |
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.
When integrating auto-save functionality via this plugin's API, the only way to keep track of whether auto saving is enabled is by creating event listeners for the enable and disable event and tracking the state in an external field. To make state tracking a little easier, I've added an
enabled()function for fetching the current state directly via the plugin's API.Examle use case
Integration with
snacks.toggle: