Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve handling of error cases where expression or context node are unspecified or invalid #137

Merged
merged 4 commits into from
Dec 16, 2023
Merged

Improve handling of error cases where expression or context node are unspecified or invalid #137

merged 4 commits into from
Dec 16, 2023

Conversation

JLRishe
Copy link
Collaborator

@JLRishe JLRishe commented Dec 16, 2023 •
edited
Loading

Now throwing helpful errors when:

  • The xpath expression is unspecified
  • The xpath expression is not a string
  • The context node is unspecified in a situation where one is needed (there are situations where one is not needed)
  • The context node is specified but not node-like

@JLRishe JLRishe merged commit 4c181e8 into master Dec 16, 2023
@JLRishe JLRishe mentioned this pull request Dec 16, 2023
Closed
@JLRishe JLRishe deleted the noexpression branch December 16, 2023 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@JLRishe