-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add support for specifying a predicate to find a specific element #38
Add support for specifying a predicate to find a specific element #38
Conversation
This will need readme updates and tests. |
It should also be added to |
bc09f7b
to
d02085f
Compare
I added this to the readme, but I can't run the tests locally since it seems like the
Done |
On an unrelated note, is there a reason to maintain a separate |
Yes. I don't like TS. I only provide types for user convenience. (sindresorhus/ky#321 (comment)) |
d8b13ac
to
77b3176
Compare
77b3176
to
339ba85
Compare
8dc7b0c
to
ed957e5
Compare
Generally, don't force push in pull requests, it also makes it harder to review what changed. |
I've re-added them in add7485. If I understood correctly - with the last push all that was overridden was the missing Please LMK if I missed anything. |
There were a few other changes too. Just look at the diff I commented. |
Right, but there were also the suggestion, so I think that together we're all aligned now: https://github.com/sindresorhus/element-ready/compare/8dc7b0c24363479246a6a2b4b3cf3d6da6f968c4..add7485 |
I committed some small tweaks. |
The "check elements against a predicate" test is failing though. |
Fixed in cd1f75a. There were some errors due to some renaming I did while working on the tests, and using a non-existent property on the element in the assertion. Funnily enough, these errors would've been caught by TypeScript. |
Thanks :) |
fixes #37