-
Notifications
You must be signed in to change notification settings - Fork 374
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
Force error during parsing #261
Comments
Hi @farski - I'm not 100% sure I understand your question, so let me know if this isn't what you were wondering... I think there's a couple things going on here that I'd like to clarify. The first is that I'm not happy at all with the callbacks in Feedjira and I'm actually moving away from them anyway. If you check out the The other part of your question - do I have data that will cause a parsing error other than Anyway, hope that helps and let me know if you have any further questions! Jon |
So the |
Yes, this is my criticism of the callback technique. There are situations where a user will assume their callback will fire and it doesn't. I much prefer the straightforwardness of rescuing exceptions. |
Hi @farski, I'm going to go ahead and close this one - let me know if you need anything else. |
I'm trying to make sure I'm handling parse errors properly, but I can't seem to get the error to happen. I either raise a
NoParserAvailable
exception, or it parses as best it can but doesn't call the error block. Do you have any example data that will cause a parsing error? I looked through the tests, but didn't see anything.The text was updated successfully, but these errors were encountered: