Moritz Jung
Moritz Jung
I just had an idea on how to handle enabled scripts that are not in the scripts folder. They should be shown below in their own list with small warning...
I feel like at this point there are too many tradeoffs with using a folder inside of `.obsidian`.
> updating the view after changing the folder You could use the `focusout` event for that. > When to remove files from startupScripts The best solution would be to show...
It is doable. A lot of API won't work in publish, but we could just throw a custom error that says that this API method is not available in publish.
The approach would be similar to what I did in Meta Bind.
I think the only thing missing from the Obsidian Publish API for JS Engine are modals. Everything else should be doable with the minimalistic existing APIs.
This is probably caused by dataview updating the code block when the frontmatter changes. Do you see the same behavior with the PF2e encounter calculator example in the example vault?
Can you share a minimal example of the issue, with as little extra fluff as possible?
For @sweetcornwhiskey's example, the behavior is expected. Typing a character into the text field updates `test_tag`. The `meta-bind-js-view` code block is set up to rerender when `test_tag` updates. So the...
> Having input text fields that live in JS contexts and are writable would be extremely helpful. They do work, with the limitation that you can't bind to properties that...