Skip to content

Revert "Store saved views as records (obsidian.base, mdbase.view)" - #177

Merged
callumalpass merged 1 commit into
mainfrom
revert/bases-as-records
Sep 29, 2026
Merged

callumalpass merged 1 commit into
mainfrom
revert/bases-as-records

Conversation

@callumalpass

Copy link
Copy Markdown
Owner

Reverts #176.

On hosted collections, a Base stored before setup is a hosted view resource, not a record. After a user approves the new base record-extension setup, read of that Base fails (file_not_found), update returns 404 record_not_found, and a newly created .base record is not returned by list_views. I reproduced this against the hosted provider on the production mdbase-rs revision. Saved-view editing in TaskNotes therefore breaks on hosted collections, while tasks and listing and running existing views keep working.

This restores the previous release, which edits views through the saved-view source operations; they work on local and hosted collections, including collections that already approved the setup. The change re-lands after the hosted provider treats Bases and mdbase views as records.

@callumalpass
callumalpass merged commit d1cdb51 into main Sep 29, 2026
3 checks passed
callumalpass added a commit that referenced this pull request Sep 29, 2026
* Reapply "Store saved views as records (obsidian.base, mdbase.view) (#176)" (#177)

This reverts commit d1cdb51.

* Use mdbase connect beta119

beta119 stores hosted Obsidian Bases as records once setup adds base, so
saved-view editing through the record operations works on hosted
collections as well as local ones.
@callumalpass callumalpass mentioned this pull request Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant