TeamNewPipe / TeamNewPipe/NewPipeExtractor
NewPipe REST APIs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 602
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 6
Description
Hi,
I have tried to create REST APIs for NewPipeExtractor.
This could be used for porting NewPipe to other platforms as discussed here.
The current implementation is just returning the POJOs as json.
It would be interesting to get your feedback.
@theScrabi @TobiGr @TheAssassin @mauriciocolli @PrestonN @omarroth
Code - https://github.com/yausername/NewPipeREST
Swagger UI (Documentation) - https://app.swaggerhub.com/apis-docs/yayausername/new-pipe_rest/1.0.0
Test Server - https://newpipe-rest.herokuapp.com/api/v1
OpenAPI spec - https://github.com/yausername/NewPipeREST/blob/master/docs/openapi.yaml
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
Start by reviewing the linked NewPipeREST implementation, its Swagger UI, test server, and docs/openapi.yaml. Compare the proposed REST API with NewPipeExtractor and the discussion in NewPipe issue #1051, then seek a defined, maintainer-approved scope before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100