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

More flexibility in choosing the files to process #27

Open
johann-petrak opened this issue Sep 18, 2019 · 0 comments
Open

More flexibility in choosing the files to process #27

johann-petrak opened this issue Sep 18, 2019 · 0 comments

Comments

@johann-petrak
Copy link
Owner

Currently all the extensions defined for any of the file types are processed (and in addition the extensions added for a type).

As we add more types, it becomes more likely that this is not wanted or that extensions can be used for several different types.

So it would be good to limit what is processed by type, by extension, or even exclude whole file path patterns. On the other hand it may be useful to define file path patterns which should be processed in a particular way (so maybe because of the base name, not just the extension).
One example is something like "robots.txt" which is a specific type of file, but not just a general text (.txt) file.

For this it may also be useful to change the way how file types are defined to not just use the last extension but arbitrary path patterns, of which extensions are a special case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant