This repository was archived by the owner on Jul 21, 2022. It is now read-only.
Open
Conversation
lawschlosser
force-pushed
the
CT-931-negative-frame-numbers
branch
from
f105679 to
c5f2ed8
Compare
- updated frame regex validation to allow for negative numbers - swap lsseq lib with fileseq lib (which supports negative frames) - removed the space char as an allowed character in frame_range string (fileseq lib does not support it)
lawschlosser
force-pushed
the
CT-931-negative-frame-numbers
branch
from
c5f2ed8 to
3daff14
Compare
flebel
approved these changes
Apr 18, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(fileseq lib does not support it)