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 👍
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 👍