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.

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

Throw exception instead of returning null when Groovy can't be found (closes #210) #211

Merged
merged 1 commit into from
Feb 15, 2022

Conversation

keeganwitt
Copy link
Member

@keeganwitt keeganwitt commented Feb 15, 2022

This improves the error messaging by avoiding NullPointerExceptions that were causing confusion and throwing our own exception instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant