You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, sorry for filing all the tickets. I'm really just playing around and stress testing it a bit 馃槃
More than once I've run into the following stacktrace while switching to preview:
2index.html:9045 Uncaught (in promise) TypeError: Cannot read property 'tags' of undefined
at TagIndex.eval (eval at <anonymous> (app.js:1), <anonymous>:9045:31)
at step (eval at <anonymous> (app.js:1), <anonymous>:68:23)
at Object.eval [as next] (eval at <anonymous> (app.js:1), <anonymous>:49:53)
at eval (eval at <anonymous> (app.js:1), <anonymous>:42:71)
at new Promise (<anonymous>)
at __awaiter (eval at <anonymous> (app.js:1), <anonymous>:38:12)
at TagIndex.reloadFile (eval at <anonymous> (app.js:1), <anonymous>:9038:16)
at eval (eval at <anonymous> (app.js:1), <anonymous>:8860:90)
at step (eval at <anonymous> (app.js:1), <anonymous>:68:23)
at Object.eval [as next] (eval at <anonymous> (app.js:1), <anonymous>:49:53)
Most recently it was while building the following dataview (not sure if it's related though):
task from ""
where file.day
sort file.day desc
The text was updated successfully, but these errors were encountered:
Interesting. Looks like some files have no metadata in the Obsidian cache, so need to add a null check. Probably worth revisiting my index code and add some extra null safety pre-emptively. Will be fixed in 0.1.6.
I believe I've fixed most of these; it was an issue with how I parsed tags (I did it in different ways when a page was first indexed, and when it was later re-indexed due to a changed).
Hi, sorry for filing all the tickets. I'm really just playing around and stress testing it a bit 馃槃
More than once I've run into the following stacktrace while switching to preview:
Most recently it was while building the following dataview (not sure if it's related though):
The text was updated successfully, but these errors were encountered: