TeamNewPipe / TeamNewPipe/NewPipeExtractor
Add proper HTTP response code validation throughout the codebase
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 602
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 6
Description
Checklist
- I am aware that this issue is being opened for the NewPipe Extractor, NOT the app, and my feature request will be dismissed otherwise.
- I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Issue Feature for tracking all PRs of this
Almost all code that uses the Downloader does not do any checking on the response code: therefore errors and exceptions thrown due to error response code give false information.
This issue is to track the development of adding proper response code validation throughout the extractor.
This issue will be deemed complete once every http network call in the codebase has proper error handling for checking the HTTP response code.
Why do you want this feature?
Better diagnostics and error handling
Additional information
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by inventorying HTTP network calls that use the Downloader and determine how response codes are currently handled. Done means every HTTP call in the extractor validates the response code and provides appropriate error handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100