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.

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

Add option to prefix archived nzbs with archive filename #2485

Closed
wants to merge 1 commit into from

Conversation

EdwinKM
Copy link

@EdwinKM EdwinKM commented Mar 5, 2023

No description provided.

@Safihre
Copy link
Member

Safihre commented Mar 5, 2023

Unfortunately I do not think I want to add a new Special switch for this. The use case is just too niche.
However, I understand your problem and I think the best solution would be to make it available in the pre-queue script. I can see if I can get that fixed for you!

@Safihre Safihre closed this Mar 5, 2023
@EdwinKM
Copy link
Author

EdwinKM commented Mar 5, 2023

I did not like the idea to put the information in the nzo because it really is not information about a nzb. But maybe you do have a cleaner solution.

Secondly. Just to learn. The source code validator spew a error about the "indent"? It does not understand the "if/else" before it?

@jcfp
Copy link
Member

jcfp commented Mar 5, 2023

I did not like the idea to put the information in the nzo because it really is not information about a nzb. But maybe you do have a cleaner solution.

Details about its origin (whether it was part of some archive of nzbs, and if so, the name of that archive) is info about a specific nzb. Info it may have in common with other nzb files from the same archive, but still.

Secondly. Just to learn. The source code validator spew a error about the "indent"? It does not understand the "if/else" before it?

Black doesn't just validate Python syntax but enforces certain formatting, line lengths, and so on. In this case, it doesn't like the extra space at the end of that line.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants