Question: Inconsistency in the representation of the path property for nested objects in rules

[bailarohit55]

When creating rules manually in code, I use '$.' to denote the outermost object in the path property of a condition, following the json-rules-engine documentation. However, I’ve noticed that when I create a rule for a nested property using the editor, it prepends the path with '.' instead of '$.'. This inconsistency is confusing and could potentially lead to errors. Could you please clarify the correct usage or consider aligning the editor’s behaviour with the json-rules-engine documentation?
Also, thank you for the editor. It has helped 👍

[vinzdeveloper]

Thanks for spotting. i agree, it should go with "$." when processing path params of object. it will be fixed in next version.

[bailarohit55]

Great! Thanks for the update.