dvField does not work with bracketed inline fields

[ssBandit]

Dataview has 3 ways to mark the data:

name:: 5
[name:: 5]
(name:: 5)

(with the last 2 being decorative that it uses for styling)

But tracker only supports the first type.
The following gives a "No valid Y value found in notes" error for all expect the first option

searchType: dvField
searchTarget: name
line:

After some probing I think the way to fix it is to just adjust the regex it uses to find the target to include possible brackets.

(^| |\t)\*{0,2}name\*{0,2}(::[ |\t]*(?<value>[\d\.\/\-\w,@; \t:]*))

           V                                                                 V
(^| |\t)(\[|\()?\*{0,2}name\*{0,2}(::[ |\t]*(?<value>[\d\.\/\-\w,@; \t:]*)(\]|\))?)

(only tested in an regex tester with some brackets and spaces combos. could be some edge cases I don't know about)

For now the workaround I found (besides doing a regex search) is to put a space after the opening bracket and a newline before the closing one. This keeps the styling and tracker can see it.

[ name:: 5
]

[wealthychef1]

I think that given the plugin's claim to support dataview data fields, this is more properly classified as a bug in either the documentation or the code.

[TomHall2020]

Just bumped into this on my first pass of trying to use the plugin, I pretty much exclusively use the [bracketedfield:: value] syntax so it took me way too long to figure out that it was the brackets causing the problem. Does this just need someone to PR the regex adjustment suggested?

[ramarivera]

Just bumped into this on my first pass of trying to use the plugin,

Seconding this, it took me too much time to realize that I wasn't doing things wrong but rather the plugin couldn't read [ ] dv fields

[kassiezimme]

Upvoting this

[agiledivider]

Another problem wit dvFields i found, is that the frontmatter items are ignored. While data view uses either frontmatter or the special syntax for data view, tracker does not.

Best solution would be to actually get the data from the data view plugin. I don't know if that is possible or not.

[don-smith]

It's also worth noting dvField does not work if the field is in the cell of a markdown table because of the pipes | used to construct the table.

[solpyro]

It's also worth noting dvField does not work if the field is in the cell of a markdown table because of the pipes | used to construct the table.

If you include spaces around the pipes, the existing regex should pick up dvFields inside a table, as shown here: https://regex101.com/r/hPKqvw/1

And that functionality if preserved with the suggested regex also: https://regex101.com/r/CgdutD/1

Finally, this further modification to the regex could also match any data field 'closely' wrapped in a table:

--------vvv
/(^| |\t|\|)(\[|\()?\*{0,2}name\*{0,2}(::[ |\t]*(?<value>[\d\.\/\-\w,@; \t:]*)(\]|\))?)/gm

Also tested here: https://regex101.com/r/KnsKYL/1

I agree with @agiledivider that pulling the data directly from the dataview engine would be preferable, especially since, as I understand it, inline fields can overwrite frontmatter data, so searching frontmatter and dvField separately might yield different results. But maybe for now we could patch the regex with either the original regex or my suggestion, as a bug fix, and take the dataview direct integration as a future feature?