Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[enhancement]: support Torznab o=JSON #15018

Open
1 task done
garfield69 opened this issue Jan 26, 2024 · 5 comments · May be fixed by #15036
Open
1 task done

[enhancement]: support Torznab o=JSON #15018

garfield69 opened this issue Jan 26, 2024 · 5 comments · May be fixed by #15036
Labels
Enhancement Needs C# PR Welcome! We would welcome a volunteer to prepare a PR to solve this problem!

Comments

@garfield69
Copy link
Contributor

garfield69 commented Jan 26, 2024 •
edited

Is there already a request for your feature?

  • I have checked older issues, open and closed

Is your feature request related to a problem? Please describe.

The Torznab specifications allow for responses to queries to be returned in either XML or JSON layouts.
https://torznab.github.io/spec-1.3-draft/external/newznab/api.html?highlight=json
Jackett currently only supports XML as this was the first format provided (is aligned with the RSS responses).
Recently there has been requests for the JSON response to be made available.

Describe the solution you'd like

For the Torznab API to support o=JSON, and if it is not already able to do so, support the o=XML parm too, to return the current default response.

Describe alternatives you've considered

n/a
@garfield69 garfield69 added Enhancement PR Welcome! We would welcome a volunteer to prepare a PR to solve this problem! Needs C# labels Jan 26, 2024
@mynameisbogdan
Copy link
Contributor

There is even anything that makes use of JSON?

@garfield69
Copy link
Contributor Author

I doubt it, since any app developers would not have had any choice up to now, its XML or bust. But if JSON was also available then perhaps that would change. ;-)

@aymene69
Copy link

This would be insane.

@BorisGerretzen BorisGerretzen linked a pull request Feb 3, 2024 that will close this issue
Open
@BrindenRobinson007
Copy link

@garfield69 What's the use case for this feature?

@mynameisbogdan
Copy link
Contributor

To use the torznab spec with JSON as an alternative to XML.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement Needs C# PR Welcome! We would welcome a volunteer to prepare a PR to solve this problem!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[enhancement]: support Torznab o=JSON BorisGerretzen/Jackett
4 participants
@mynameisbogdan @garfield69 @aymene69 @BrindenRobinson007