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

Feature Request | -[u]f file save as name #424

Open
1 task done
spirillen opened this issue Mar 26, 2025 · 0 comments
Open
1 task done

Feature Request | -[u]f file save as name #424

spirillen opened this issue Mar 26, 2025 · 0 comments
Assignees

Comments

@spirillen
Copy link
Contributor

What is the feature you'd like to request?

I'm not entirely sure how to articulate this, so I'll present it in a straightforward manner. Here’s the issue:

In the @mypdns/matrix project, I use the same filename across different folders that represent various categories.

pyfunceble -f https://github.com/mypdns/matrix/raw/refs/heads/master/source/movies/wildcard.csv https://github.com/mypdns/matrix/raw/refs/heads/master/source/porn_filters/explicit_content/wildcard.csv

For instance, when I test source/movies/wildcard.csv and source/porn_filters/explicit_content/wildcard.csv, both files test results, are currently saved as output/wildcard.csv/. This creates a problem, as it becomes impossible to differentiate the results corresponding to their respective sources.

To resolve this, I need a way to ensure that the output files are saved in separate folders based on their source categories.

What problem are you trying to solve?

A method to separate the output from sources with the same filename into distinct results folders.

What solution would you like to see?

I'm not entirely certain, but my initial thought was something along the lines of -f ["source", "save_as"], along with reading from JSON or CSV files with this grouping.

We should bear in mind that PyF is utilised for both CLI and CI/CD purposes.

Are there any alternatives you've considered?

No response

Additional context

By organising the results in this manner, you begin to move away from the 70-year-old and outdated RFC 952 hosts file and towards something more modern, such as RPZ, with support for separated test results. Consequently, this should also mark the point at which domains are regarded as unique rather than the source. The source merely serves as a relation to the domain (record) being tested within its grace period, identified by --dbr n.

Code of Conduct

  • I agree to follow this project's Code of Conduct
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants