Skip to content

fix solhint warnings for custom errors #1639

fix solhint warnings for custom errors

fix solhint warnings for custom errors #1639

Triggered via push February 3, 2025 11:19
Status Success
Total duration 3m 36s
Artifacts

security-ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
solhint: contracts/lib/Poseidon.sol#L2
Found more than One contract per file. 8 contracts found!
solhint: contracts/lib/SmtLib.sol#L2
Found more than One contract per file. 2 contracts found!
solhint: contracts/validators/request/CredentialAtomicQueryV3Validator.sol#L8
imported name IState is not used
solhint: contracts/validators/request/CredentialAtomicQueryV3Validator.sol#L295
Rule is set with explicit type [var/s: uint]
solhint: contracts/validators/request/CredentialAtomicQueryValidatorBase.sol#L224
Use Custom Errors instead of revert statements
solhint: contracts/validators/request/CredentialAtomicQueryValidatorBase.sol#L242
Use Custom Errors instead of revert statements
solhint: contracts/validators/request/CredentialAtomicQueryValidatorBase.sol#L253
Use Custom Errors instead of revert statements
solhint: contracts/validators/request/CredentialAtomicQueryValidatorBase.sol#L260
Use Custom Errors instead of revert statements
solhint: contracts/validators/request/CredentialAtomicQueryValidatorBase.sol#L270
Rule is set with explicit type [var/s: uint]
solhint: contracts/validators/request/CredentialAtomicQueryValidatorBase.sol#L276
Use Custom Errors instead of revert statements
coverage
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/