Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve clarity and performance of collateral Non-ADA validation: #3574

Merged

Conversation

lehins
Copy link
Collaborator

@lehins lehins commented Jul 25, 2023

Description

Predicate checks are lazy in their argument, because it is possible to run STS rules without doing any validation. Current Non-Ada validation ignored this capability and forced validation regardless of the options provided to the STS runner, which this PR fixes.

This commit also improves the clarity on the implementation of validation, by explaining all possible cases.

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated
  • When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
    versioning process.
  • The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
  • Code is formatted with fourmolu (use scripts/fourmolize.sh)
  • Cabal files are formatted (use scripts/cabal-format.sh)
  • hie.yaml has been updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

@lehins lehins force-pushed the lehins/avoid-collateral-validation-when-no-validation branch from fb3fc5d to af267ac Compare July 25, 2023 15:38
Copy link
Contributor

@teodanciu teodanciu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

Predicate checks are lazy in their argument, because it is possible to
run STS rules without doing any validation. Current Non-Ada validation
ignored this capability and forced validation regardless of the options
provided to the STS runner.

This commit also improves the clarity on the implementation of
validation, by explaining all possible cases.
@lehins lehins force-pushed the lehins/avoid-collateral-validation-when-no-validation branch from af267ac to 41882c7 Compare July 26, 2023 20:55
@lehins lehins enabled auto-merge July 26, 2023 20:55
@lehins lehins merged commit d1a76bb into master Jul 26, 2023
@iohk-bors iohk-bors bot deleted the lehins/avoid-collateral-validation-when-no-validation branch July 26, 2023 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants