add no-stack-checks
to kontrol.toml
file
#867
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.
Add the
--no-stack-checks
option to the toml file generated when a new project is created.Additionally, this PR inverses the
dest
for the flags starting with--no-...
with thedest
also starting withno_...
, such as--no-metadata
, which is now used to setmetadata
(instead ofno_metadata
)--no-silence-warnings
--no-forge-build
--no-stack-checks
The logic of this flag processing is changed accordingly.
The reason for this changes is due to the way parse_toml_args handles options starting with
no-
in thekontrol.toml
file: it strips theno-
, and sets the remaining option string to the negation of the argument provided. That's needed to accommodate options such asBut prevents
no-stack-checks
and other similar args from being parsed correctly.