Defaulting findElorEls to single element #53
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
users won't be using this API directly so I don't think it matters much. they'll be hitting the session via an actual client which this change doesn't affect. |
|
I agree. If it makes the test code feel cleaner, I'm fine with the change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@imurchie on second thoughts, I think the benefit from defaulting to false (i.e. requesting a single element) will be outweighed by potential confusion for the user.
The old API had
elementByClassNameandelementsByClassName. If these are removed, it might make sense to train the user from the beginning to specify single or multiple elements.I'd be curious to get your thoughts.