TypeError: container.parent.execute is not a function #46
Comments
segovia
added a commit
to segovia/webdriverio-testing-library
that referenced
this issue
Jan 4, 2023
|
Here is the pull request. You are free to edit the commit. The naming might be sub-optimal. |
|
@segovia Thank you very much for raising this! I'll have a look at your PR as soon as I get the chance 🙌 |
olivierwilkinson
pushed a commit
that referenced
this issue
Jan 16, 2023
Closes issue #46. When using WebdriverIO v8 we encounter `TypeError: container.parent.execute is not a function`. This is due to the execute function being moved off of Elements. Traverse up through the Element's parents until we find one with `execute` and use that to inject DTL and to execute the query. Using the parent to execute does not change the behaviour of `within` since the passed Element is still used as the container for the query.
|
Since the code was merged, do we have a release in sight? |
Yup! Sorry I was looking to release and got caught up fixing the builds again. |
|
@segovia this has just been released, sorry for the delay! You should be able to use v3.2.1 now 😄 |
|
That's awesome! Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The error in the title "TypeError: container.parent.execute is not a function" happens with webdriverio v8 when you use a testing library query nested within another element.
I believe this issue is related to the fix done for: #42
I have a proposed solution that I will link in the comments.
The text was updated successfully, but these errors were encountered: