-
Notifications
You must be signed in to change notification settings - Fork 21
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
create --inputDir
and --outputDir
for --transform
#39
Comments
added to The transformation has been split into options The transformation loops over all files of type The directory names are defaulted from the NormaTransformer.Type We will wait for reaction and bugs before closing |
I don't think you have committed your code. I couldn't see it either here or on your petermr fork. I think I can see the use of this option but I'm not sure that adding yet another two options to our very long list is a good idea. For example having --inputDir is very similar to the CProject concept. Could the same effect not be achieved with file globbing? Also, I'm hesitant (since I've not seen the code) as to what transformDirectory and transformSingleInput do. I think all the transforms should probably really be a "single input" and we should just run many of these to transform a whole directory. I think having a table of what we can do and what the default input and output options are stored in an enum is probably a good idea but it does reduce the consistency considering all of the command line options are stored in args.xml. |
Code compiles and doesn't test. |
These arguments would allow transformation of subdirectories (e.g.
table/
,image
) which contain multiple files of the same type.The text was updated successfully, but these errors were encountered: