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.
Being able to set a keyword value for an element is especially useful for page object implementations. Rather than trying to match the selector output to a defined method, the user can now just look up the name of the element assigned. It would need to be implemented in the Page Object gems, but this provides the necessary hook for that.
Also, I changed the error messages to use
#selector_string
when really they should be using#inspect
like was there before.#selector_string
is still recursive, but#inspect
includes information about "located", "class name" and the new "keyword." (I removed the memory information; that is still available withElement#to_s
if anyone cares about it).