-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assert.dom(Element).exists() throws even if it exists #245
Comments
hmm, interesting, I was pretty sure I implemented it that way at first. Has this possibly changed lately? |
Not sure - |
thinking some more about it, why do you use
it does, but not all assertions support it. just like with e.g. chai when you |
I just came up against this issue using |
Bumping this... We see the error with |
I also encountered this with |
Just to clarify, are folks encountering this issue using Typescript in their projects, and they're getting a type mismatch? |
I’m getting this in an Ember project, not using Typescript. |
@scalvert it's been a while since I've commented but we don't use TypeScript |
Let me take a peek again and see if there's anything outstanding we need on that PR. |
Sorry that everyone's been encountering this issue. I'm working on it now, and just adding a number of test cases to ensure that our fix is working. |
Ready to go! Just waiting for a merge/release. Thanks for your patience, everyone! |
Even though officially the
dom
method accepts theElement
type, when using it that way theexists
method ends up throwing an error, even if the element exists. At root, this is becauseexists
callsfindElements
, which is not currently set up to check forthis.target
being anything other than a string.I have a PR inbound shortly to add support to
findElements
for having Element targets, but wanted to track it here also.The text was updated successfully, but these errors were encountered: