fix: add warning for invalid unstable feature use in deno.json/jsonc #24120
Conversation
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
|
|
dsherret
reviewed
Jun 6, 2024
|
Hello @dsherret , |
|
Hello @dsherret , |
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.
Added warning message when using invalid unstable feature within deno.json or deno.jsonc
The commit is made to address issue #21987 .
Code changes
A) Added logic to compare the used unstable features within deno.json with the supported/valid unstable features to decide to whether warn or not.
_P.S: The Supported features were retrieved from (UNSTABLE_GRANULAR_FLAGS) within deno/runtime/lib.rs and the rest of the flags (bare-node-builtins, byonm, sloppy-imports) by refering to the link_
B) Added test to make sure the issue is solved compeletely. Test: deno\tests\specs\task\invalid_unstable_feature
@littledivy