It’s currently very easy to accidentally hit the “X” next to a list item in a Base, and without an Undo feature, this can make it kind of anxiety-inducing to even have a Base open. Doubly so on mobile, where an undo feature would be hard to access.
Proposed solution
Like with normal pages, I would love to just toggle on a “Reading view”. And embedded Bases could inherit this property from the page they’re embedded into.
Quick overview, I have a table displaying customer data (names, addresses, etc) which I don’t want to modify from within bases/table view, I only want to view. When displaying a list within the table, each list item has an X to remove it, which means it could be possible to accidentality delete list entries by mistake.
I want to be able to prevent this happening, some ideas:
Being able to view in source/preview, same as notes, can only modify in source mode.
Being able to “lock” columns to prevent changes
Apologies if I’ve missed that this is already a function
A bit more cumbersome than using CSS but I think another workaround could be to rely on formula properties in a dedicated view to get the desired properties displayed …
I mean, instead of simply selecting a key to add in the base (using the Base GUI), one can create a formula property and use something like myProp in the formula box to display its value which would be somewhat uneditable/read-only (afaik/iirc ) as one would need to edit the formula first to edit the values it displays (or update the values of the property in the relevant notes).
Here’s a time on Discord. In case you don’t have an account and the insider’s badge to see it yourself, I’ll paste the chat below.
I don’t recall if that’s the comment I saw four months. And I don’t know the team’s future plans. It’s merely what showed up in a search just now.
our fellow Obsidian user:
Is a read / edit mode planned for bases? Or at least for when a note is in read mode? I just noticed it’s pretty simple to remove a tag from a list, and thus a embedded base.
kepano:
No, bases will still be editable in read mode, like checkboxes and properties
but this is easy to change with a snippet if you want
Under my current Obsidian version, this code no longer allows for clicking on the “file name” link column to visit a file. I can click on tags, however. I think this worked before . . . did something change?
Glanced at the DOM in v1.11.4, and it looks like deleting .multi-select-pill-content will take care of it.
Don’t know whether both text links and multi-select links changed or I had just missed a comma the first time—though no one complained before, so I’ll assume a change.
Thanks for calling it out.
Will update the earlier comment after getting a chance to check that this edit works for various links—file, lists, multiselect pills—and that no additional selectors have become unnecessary. Feel free to call out any other issues you encounter with it.