fix: set-default no longer fails when obsidian.json is missing or unparseable#1
Merged
Conversation
…arseable Two fixes: - vault_path.go: if vault name is an absolute path, return it directly without reading obsidian.json (handles the common case of storing full paths as the default vault) - set_default.go: path resolution after setting the name is now best-effort; a warning is printed instead of a fatal error, so the command always succeeds as long as writing preferences.json works
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.
fix: set-default no longer fails when obsidian.json is missing or unparseable
Description
Two fixes:
Motivation and Context
fix a bug
Checklist: