CLI: Add --seed=true
to generate a new seed
#1800
Merged
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.
--seed
to require a value.This fixes the conflict with test file arguments, raised in CLI --seed without value and files argument is counterintuitive #1691.
--seed=true
to generate a new seed.This makes it consistent with URL Params, where
?seed
(which translated toseed=true
) already did this. With this patch, we now also support pre-configqunit_config_seed=true
andqunit_config_seed="true"
. As well as--seed=true
on the CLI. And URL param?seed=true
(in case someone tries/expects that).While at it, this also:
/src/core/config.js
, by translating--seed
to a preconfig.Fixes #1691.