Closed pwkooij closed 3 months ago
detail is (currently) just a string, and item rarity/tier is only separately available as tags.
When an attribute has sub-attributes, I try to be clear about it in the docs, e.g.
sourceAndPage
Book sources as list of SourceAndPage
The latter SourceAndPage link shows the sub-attributes. I realize I was not clear in the detail description that it was a pre-formatted string containing those attributes.
Will think about how to capture those as sub-resources, they are not always present.
Thanks for the clarification! I would love to be able to add the rarity separately in the frontmatter to make it easier to parse with dataview
You can already parse with dataview, as tags are supported natively and you have those.
I guess I have to go back study on how to use that hehe! Thanks again! And wow you respond fast! Not used to that on github, much appreciated!
I am trying to add item rarity in the frontmatter, but I am not able to seem to pick up the information, and instead it throws an error.
I have tried several codes using resource.rarity or resource.detail.rarity, but I'm not able to extract that information
I would like the frontmatter output of the item to look like this:
When I add the text as described above in the template file it results in the following errors for
{resource.rarity}
: [ š ERR] io.quarkus.qute.TemplateException: Rendering error: Property "rarity" not found on the base object "dev.ebullient.convert.tools.dnd5e.qute.QuteItem" in expression {resource.rarity}and for `{resource.detail.rarity} [ š ERR] io.quarkus.qute.TemplateException: Rendering error: Property "rarity" not found on the base object "java.lang.String" in expression {resource.detail.rarity}
Configuration
Sources:
log file with run that included {resource.rarity} ttrpg-convert.txt