hananoshikayomaru / obsidian-incomplete-files Goto Github PK

app.js:1 Uncaught Error: element or incompleteFilesContainer is null
    at isFileInView (plugin:incomplete-files:16508:11)
    at eval (plugin:incomplete-files:17101:16)
    at e.tryTrigger (app.js:1:695499)
    at e.trigger (app.js:1:695432)
    at t.trigger (app.js:1:713365)
    at t.onChange (app.js:1:703783)
    at e.trigger (app.js:1:610660)
    at e.<anonymous> (app.js:1:608471)
    at app.js:1:237027
    at Object.next (app.js:1:237132)

_YOM-565

null

_YOM-557

you can see that the files opened are wrong.

_{From SyncLinear.com | YOM-586}

or other status: complete, we should let user choose how they want the yaml to be.

_YOM-554

null

_YOM-593

null

_YOM-556

null

_YOM-592

this writing style will make the plugin think that it is not complete. But in Obsidian, this writing style is not recognize as a valid heading.

✅ / ❌ we need to determine whether we should follow the markdown definition or obsidian definition.

current file / total files (percentage) this is needed otherwise user might not know when will that end.

_YOM-588

if there are comments, ignore it, still count as empty.

_YOM-577

null

_YOM-578

null

_YOM-558

given a file, run it 1000 times to check how long it takes. Then we create a benchmark of different rules. Also need to update the doc.

_YOM-587

null

_YOM-555

just like vscode highlight problematic files.

Nice plugin! Until now I used tags and checklist for notes I want to finish later. But you plugin seems like a nicer solution! Thanks!

Just wondering what you think about adding support for tags. Adding a #incomplete is maybe a good addition for people working with tags?