Ryan Emerle
Ryan Emerle
If it's as simple as adding a single option, let's just do it.
Seems reasonable if the fix is in line with #563. Moving to ready.
@JanuszU You are looking for group-based security around selecting the backend for a zone? Can you provide your use case? I can think a few, just curious what you're solving...
Should be worth reproducing and fixing if it reduces issues with development.
> As a tech project, would like to explore changing to http4s as part of standardizing the stack. @pauljamescleary What's the benefit of moving to http4s? How does this standardize...
Yeah, it would be great to not have to worry about processing the effectual actions. The fewer `unsafe*` calls that the devs have to make, the fewer will be made...
Longer term we should consider RBAC, and simply assign roles to groups/users. A "sysadmin" role would be a good first candidate and could replace the current concept of "super" users....
For a workaround for the broken context menu (for the Desktop app), go to your `.obsidian\plugins` folder or `Settings -> Community Plugins -> Installed Plugins` and click the folder icon:...
I have a workaround, and possibly a starting point for @chetachiezikeuzor's investigation. It seems the Obsidian API expects you to play nice with their context menus, so I suspect a...
May have been fixed by the 2.3.13 release https://github.com/microsoft/WSL/releases/tag/2.3.13