-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Use entire namespace so exception constant is resolved #243
Conversation
@parkr Thanks for the original Pull Request! Sorry we missed this in code review. 😊 |
@simeonwillbanks Thanks for catching this! Apologies for the dud. |
@simeonwillbanks 🙇 thanks for catching my mistake. @parkr no need to apologize, I should've been more thorough with the review. @simeonwillbanks would you be open to releasing a patch release? |
@jch prepping release... |
Use entire namespace so exception constant is resolved
Thank you, @simeonwillbanks! 🎉 |
🎉 On Sun, Jan 17, 2016 at 2:47 PM, Parker Moore [email protected]
Jerry Cheung |
😉 |
Problem
#241 introduced a custom exception, but it used the exception outside the
HTML::Pipeline
namespace.Solution
Resolve the exception constant by using the full namespace.
/cc @parkr @jch