Add support for objects (dot notation) in card requirements #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes in this branch add support for objects (using dot notation) within card requirements. The changes work in both tag and comment style requirement syntax. I added minimal examples of both approaches. The comment style example is a copy of your card with covers example. The only change is that it uses of $pc.strength rather than $strength. The simple dot notation example using the text and most of logic behind that same example. However, I did not include any of the code for the covers in order to keep things as simple as possible. I added one extra option (sneak past the beast) so that the player character could have more than one property. All javascript and examples have been rebuilt, unlike my last commit.
I was unable to figure out how/where to put the object/dot notation change within the brief docs summary.