-
Notifications
You must be signed in to change notification settings - Fork 43
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
Feature/improve error msg #388
Conversation
…f complex But then they show a misleading error message...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We definitely need more tests, at least one for each specification. Therefore I would split this PR, have a better, more reliable and understandable error message and increase support for the specification (the same goes for XPath).
1a7bea3
to
2c820b9
Compare
Agreed. I reverted the last commit on this branch and have a separate branch. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to log and silently ignore the unsupported selectors (which would fix the error). This would then just not apply the unbreakable, but will itself not break with an exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use assertj-core for assertions.
3dd399a
to
9805c4e
Compare
Improve error message to resolve #303