0.3.0 — the wiki moves into Javis-wiki/
The wiki now lives in one folder, Javis-wiki/, instead of nine folders at the root of your vault.
Changed
- Wiki pages are written under
Javis-wiki/<Type>/, for exampleJavis-wiki/Concepts/Agent-Builder.md. A type folder is created only when it has pages. - Your existing wiki moves on the first sync after upgrading. Every Javis note in the old root folders (
Concepts/,Topics/,Sources/and the rest) is moved intoJavis-wiki/, including pages you edited or adopted (javis_sync: false). You see "Javis: moved N notes into Javis-wiki/." - Your own notes stay where they are. A note without Javis properties in one of those folders is not moved, and neither is a note you upload (one with a
javis_source_id). A root folder is removed only when it is completely empty on disk, hidden files included; later syncs retry if it could not be removed the first time. - Nothing is overwritten. If
Javis-wiki/already has a note with the same name, the root copy is left alone and Sync now tells you, with the paths in the developer console. - Links keep working. Page bodies still contain links like
[[Concepts/Foo]], and Obsidian resolves them toJavis-wiki/Concepts/Foo.md. No link is rewritten. - Upload folders:
Javis-wiki/cannot be chosen. Root folders namedTopics/,Sources/and so on are yours again and can be uploaded.
minAppVersion stays 1.11.4, and the plugin is still desktop-only.
Upgrading
Replace main.js and manifest.json in <vault>/.obsidian/plugins/javis-wiki-sync/ and reload Obsidian. The move runs on the next sync, including the one when the vault opens. Your settings and sign-in are untouched.
If you install through BRAT with the version frozen at 0.2.1, change the pinned version to 0.3.0: BRAT does not update frozen plugins.
Rollback
Reinstalling 0.2.1 does not move notes back. It writes a fresh copy of the wiki at the vault root next to Javis-wiki/.
Tested
668 unit tests pass. The end-to-end run in a real Obsidian 1.13.7 vault passed 16 cases and failed none: the 192-note move, edited and adopted pages, a user note left in place, folder cleanup, link resolution, clash handling, a note with broken properties, and the upload guard. Three were not run: uploading a note from a root type folder (it needs a real upload), and two optional scratch-vault cases.