Add FutureWarning for default filesetter external engines#1102
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1102 +/- ##
=======================================
Coverage 81.75% 81.75%
=======================================
Files 142 142
Lines 15611 15612 +1
=======================================
+ Hits 12763 12764 +1
Misses 2848 2848
Continue to review full report at Codecov.
|
dwhswenson
approved these changes
Jan 28, 2022
dwhswenson
left a comment
Member
There was a problem hiding this comment.
LGTM, except the one spelling change I'll enforce.
Merged
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this adds a
FutureWarningto let users know that in OPS 2.0 the defaultFileSetterwill become random stringThis was part of the discussion on #1101