deprecate config.globOptions #1152
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1152 +/- ##
=======================================
Coverage 97.27% 97.28%
=======================================
Files 36 36
Lines 1360 1361 +1
=======================================
+ Hits 1323 1324 +1
Misses 37 37 ☔ View full report in Codecov by Sentry. |
nfischer
force-pushed
the
deprecate-glob-options
branch
from
7cad93a
to
e787e1b
Compare
|
Let me see if it is possible to deprecate this but keep maintaining it for the time being (e.g., add the test cases back). I need to see if that approach will be compatible with PR #1153. |
This deprecates support for configuring `config.globOptions`. Exposing this variable makes it difficult to change (or upgrade) our glob library. This discourages users from depending on this config option going forward. If anyone is using `config.globOptions` then it should continue to function, however this support is not promised for the long-term. As far as I know, this is not a commonly used option: https://github.com/shelljs/shelljs/issues?q=globOptions currently shows no GitHub issues of users using this option, and there was never really a motivation for why this needed to be exposed (#400 exposed the option just because we could, not because we should). This is one step toward supporting Issue #828.
nfischer
force-pushed
the
deprecate-glob-options
branch
from
e787e1b
to
04a30d1
Compare
|
It does look like there's some usage of this option when I search all of GitHub: https://github.com/search?q=shell.config.globOptions&type=code So I think the plan should be: deprecate official support, but don't break existing usage. I'll remove the "breaking" label since this technically is not a breaking change anymore. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 removes support for configuring
config.globOptions. Exposing this variable makes it difficult to change (or upgrade) our glob library. It's best to consider our choice of glob library to be an implementation detail.As far as I know, this is not a commonly used option: https://github.com/shelljs/shelljs/issues?q=globOptions currently shows no GitHub issues of users using this option, and there was never really a motivation for why this needed to be exposed (#400 exposed the option just because we could, not because we should).
This is one step toward supporting Issue #828.