-
Notifications
You must be signed in to change notification settings - Fork 148
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
[Improvement] Fetch Failed related exceptions should have a dedicated RssException class #750
Comments
Thanks for the improvement. There are also many raw use of |
Yes, it's definitely worth refactor. Would you mind create an issue for this? |
### What changes were proposed in this pull request? 1. add a new exception called RssFetchFailedException 2. it's used in various instance creation ### Why are the changes needed? Fix: #750 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Existing UTs.
### What changes were proposed in this pull request? 1. add a new exception called RssFetchFailedException 2. it's used in various instance creation ### Why are the changes needed? Fix: apache#750 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Existing UTs.
Code of Conduct
Search before asking
What would you like to be improved?
Currently, a lot of exception are all called RssException, which has no distinguish meanings.
When I'm implementing #477, I think we should at least to make fetch fetch exception a dedicated subclass.
How should we improve?
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: