Clarify source folder mapping and note selection in settings - #5
Merged
Merged
Conversation
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
1 participant
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.
Settings now explain that Source folder controls where Basecamp paths begin, while Include selects which notes to publish. A concrete folder-mapping example shows the required vault paths and the resulting Basecamp location.
The descriptions also explain recursive selection, exclusions, both Preserve folders options, and the preview/publish buttons. Sync behavior and saved configuration are unchanged. Version 0.1.4 prepares the private BRAT update.
Validation:
npm run packagepasses (49 tests, lint, TypeScript, and mobile bundle checks). Checked the settings text and example in Obsidian 1.13.7 on macOS with the existing configuration retained.