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

PSL Exceptions #230

Open
eriq-augustine opened this issue Oct 30, 2019 · 2 comments
Open

PSL Exceptions #230

eriq-augustine opened this issue Oct 30, 2019 · 2 comments
Assignees
@caleblevy
Labels
Admin - Good First Difficulty - Easy Priority - Normal Type - Refactor

Comments

@eriq-augustine
Copy link
Member

Issue by eriq-augustine
Friday Oct 19, 2018 at 18:22 GMT
Originally opened as eriq-augustine#183

All exceptions we create/throw should probably derive from some common PSLException.
This way we can easily differentiate between errors that come from PSL and errors that come from elsewhere.
@eriq-augustine
Copy link
Member Author

We can also expand on this with specific types of exceptions, like UndefinedPredicateException.

@caleblevy
Copy link

I can take this one.

@eriq-augustine eriq-augustine mentioned this issue May 18, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caleblevy caleblevy

Labels
Admin - Good First Difficulty - Easy Priority - Normal Type - Refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eriq-augustine @caleblevy