Same Dataview Queries Delivering Different results or errors depending on block

[artjafri]

using dataview 0.3.8 and obsidian 0.12.3

I have had this problem pop up since yesterday, in the middle of writing a note I saw all of my dataview blocks in a separate note reload to errors(unexpected identifier). since then dataview blocks are inconsistent in behavior. re-installing obsidian or the plug-in has made no difference. My best example is this two line query that is the most widely used in my workspace with some variations in the linked page it uses as the search parameter

table Completed as "last chapter", img as IMG
from [[Reading]] 

this same query will, depending on the page return:

• only the first result that matches
• all results but results cannot be sorted, and are always in reverse alphabetical order
• an error "unexpected identifier"

Deleting the page completely and rewriting the queries seems to fix it, but im more concerned with the blocks refreshing to an error.

I did some testing it appears that editing the pages that are already showing inside a Table seems to have an effect. When changing the status of certain books from [[Reading]] to [[Finished]] those books would be removed from the "Reading" table but not show up in the "Finished" Table during subsequent refreshes of the dataview block that searches for [[Finished]].
It would return errors (unexpected identifier) for other dataview queries that were changed to search for [[Finished]] on the same page, while they would show up in a new page with a query for finished.

Once the error appears it seems localized to a page.

[mnvwvnm]

The second query use "dataviewjs", not "dataview". Dataview JS block uses a different code language.
(btw, a parallel question: how do you introduce images as metadata?)

[artjafri]

The second query use "dataviewjs", not "dataview". Dataview JS block uses a different code language.
(btw, a parallel question: how do you introduce images as metadata?)

My bad, originally all of these were dataviewjs block but after the first time I had errors i tried to rewrite. guess i thought the problem persisted for no reason. solves the syntax error but still doesnt explain why the regular dataview table will only return the first result/be unsortable sometimes.

as for the second part I have a custom inline field (outisde of YAML) called img:: and it'll pull the image link as long as its expanded like ![cover image](link). I have'nt tried it out in frontmatter, I prefer to have my metadata inline, but you can get pretty crazy results for defining custom css to the dataview return. here's my work in progress for setting up an image gallery + library like you might in notion.

[mnvwvnm]

About the sorting issue, I'm a newbie in dataview and I'm not yet comfortable with the language of this plugin. However, I have noticed that sometimes there are some problems when using numbers as text (in particular numbers with the AAAA format) and the plugin tends to read them as a date (YYYY)!
About the images, that is cool! I already tried to use the HTML format in the frontmatter or in inline field (something like <img src="file:///Users/......">) and it works... But the table turns unstable and when it does an automatic refresh the table presents some glitches (a kind of 'shakes', as a graphical issue).
When you use the format ![cover image](link) the link is an internal or external link?

[artjafri]

I use it mainly as external links. A large part of my vault is basically collections of historical artworks, and design projects. saving all of those to disk would eventually set my machine on fire. I've noticed the same issue with the table turning unstable, in my case it would it stutter and keep the page from scrolling down past a certain point. But it doesn't happen if the table has a manageable size of row (arbitrary number here, i' havent done any tests but i know not go above ~400, i did that and broke the table). Its also more unstable if youre using dataviewjs and/lots of custom css. I havent had much trouble with vanillla dataview and small css tweaks