Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi,

thanks you so much for all the work you have clearly put into this. I have an issue in section 3.3 - Obsidian won't parse it correctly and I see an error:

Dataview (inline field '>'): Error:  -- PARSING FAILED -------------------------------------------------- 
 > 1 | >     | ^  Expected one of the following:   '(', 'null', boolean, date, duration, file link, list ('[1, 2, 3]'), negated field, 
number, object ('{ a: 1, b: 2 }'), string, variable

Is this an issue with my Obsidian setup? Any idea?

Thanks in advance!

With Obsidian, the > character is a quotation block. So, it seems your DataView query is not expecting that. Without knowing the query, it’s hard to tell.

Thanks Phil. I don´t know what the query is either, I just copy/pasted the file into Obsidian. I know that Marked2 parses it correctly, but Obsidian doesn't seem to. It must be just my Obsidian as I would expect others to have the same problem, but no-one seems to.

(1 edit)

It is not “just your Obsidian”. The problem (if you call it that) is, that the Community Plugin “DataView” interprets the “=” of the “=>” as the beginning of an inline query, which is a kind of “show me all the notes, that have these contraints” request. It seems you are not using these inline query so you should be fine to change the “Inline Query Prefix” in the options for DataView to something like “==” instead of “=”.

(+1)

That did it! Thanks for your help!