-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Adding Dry Run Option #58
Labels
Comments
Valid idea, but would require an extensive refactor. |
I believe we can defer or close this feature. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@orchetect I believe right now our tool/library would throw an error during the extraction operation if it detects any.
Is there a possibility where the tool might throw an error half-way during the extraction process? Which can result with in-complete image set?
In anticipation of large complex timelines, I am wondering if adding a
--dry-run
would make sense?When enable, MarkersExtractor would perform the scan of the FCPXML base on provided switches/options without starting the image extraction. It is somewhat similar to
--no-media
#40.But the difference its, it won't create the
done.json
file at its first run. Upon successful passing of Dry Run, MarkersExtractor would perform than start the actual extraction operation.Any thoughts?
The text was updated successfully, but these errors were encountered: