This showed up while testing the event-listener-tree changes.
NOTE: This PR is just to merge into the other branch, but I wanted to make it super visible for review purposes.
It seems as if with the new changes, we no longer support using useEventObjects: true with no path provided as an argument. In the calling code I was testing, I was able to work around the issue by adding the ** path argument.
A failing test has been added here which passes with the new check I added.
I'm not sure this is the cleanest solution. Not being very familiar with this code, I am open to suggestions!
This showed up while testing the
event-listener-treechanges.It seems as if with the new changes, we no longer support using
useEventObjects: truewith nopathprovided as an argument. In the calling code I was testing, I was able to work around the issue by adding the**path argument.A failing test has been added here which passes with the new check I added.
I'm not sure this is the cleanest solution. Not being very familiar with this code, I am open to suggestions!