-
Notifications
You must be signed in to change notification settings - Fork 6
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
regular expression matching on files #11
base: master
Are you sure you want to change the base?
Conversation
I started to get the source code in |
…s Task.id. more evidence for removing Task.alias
After spending a decent amount of time coding this up and playing with it in practice, I'm not terribly convinced that this is the best way to approach this issue. Among other reasons, regular expressions are inherently difficult for users to understand and this feature adds significant complexity to the source code when the same type of functionality --- namely being able to iterate on specific cases during development --- might be more easily addressed by some combination of #52 and #44. For the time being, I'm going to abandon this feature but I'll leave the issue open for the foreseeable future in the event that others find it compelling. I just want to make sure that this will actually be useful before we unnecessarily clutter the functionality with difficult-to-maintain features. In the meantime, here's a quick list of things that I can think of that would really be required to be able to merge in this pull request.
|
from the design specification, the command line interface should have something like
to limit the
data/per_file
task to only depending on the filedata/first/a_specific_filename.dat
and only creating the filedata/per_file/a_specific_filename.dat
, as defined here: