Open mwestphal opened 3 weeks ago
Would this be the right time to rename this argument to --no-config
or something?
--dry-run
is used in many CLI applications to mean "run as normal but don't actually write/change anything" so it's a bit confusing (F3D's --no-render
is closer to what --dry-run
usually means)
Good point @snoyer
Is this issue still open? If it is I would like to work on it.
It is open!
Hum, since you are working on another issue, I'd like to keep this one open for other developpers with no experience on the project if thats ok
sure thats fine
Hey there, this looks interesting, if no one else is working on it, can i pick it up? Thank you so much! @mwestphal
Sounds good! @rehanganapathy , go for it :)
Describe the bug F3D usually uses a config file, but there is an option to disable this behavior,
--dry-run
. It seems to be non-functionnal currentlyTo Reproduce Steps to reproduce the behavior, using a built f3d with BUILD_TESTING enabled:
Expected behavior Config file should not be read
Additional context in
F3DStarter.cxx:655
, although the comment says that dry-run is being checked, its actually not. Add the check here by checking the cli option and position the boolean accordingly. Also add a test for it inapplication/testing/CMakeLists.txt