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

Exceptions that occur in plugins (aka rules) should not be reported as PARSE_ERROR #358

Closed
ryaneberly opened this issue Jul 18, 2017 · 1 comment
Assignees
Milestone

Comments

@ryaneberly
Copy link
Contributor

they should have a separate code and a message that gives the name of the plugin, and the stacktrace.

@ryaneberly ryaneberly added this to the 1.3 milestone Jul 18, 2017
@TheRealAgentK TheRealAgentK modified the milestones: 1.3.0, 1.3 Jul 25, 2017
@KamasamaK KamasamaK changed the title Exceptions that occur in plugins (aka rules) should not be reported at PARSE_ERROR Exceptions that occur in plugins (aka rules) should not be reported as PARSE_ERROR Jul 25, 2017
@ryaneberly
Copy link
Contributor Author

This has been implemented elsewhere

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

No branches or pull requests

2 participants