Overview
Currently we explicitly only support certain types for secret variables. This is specified in our documentation and there are zappify errors in case one is used in a .zol contract. However, for public variables that interact with secret variables, we will encounter the same problems, because the logic is still required in orchestration and circuits. We therefore should widen our error message to include public variables that interact with secret variables.
Tasks
Describe the solution you'd like
- Error messages for public variables that interact with secret ones that are not a supported type.
- Documentation updated to make this clear.
- Tests added under error-checks.
Optional
Describe alternatives you've considered
We could do this for all public variables but this would limit the functionaltity that starlight can achieve.
Definition of done
When is this task complete?
The above tasks completed.
Overview
Currently we explicitly only support certain types for secret variables. This is specified in our documentation and there are zappify errors in case one is used in a .zol contract. However, for public variables that interact with secret variables, we will encounter the same problems, because the logic is still required in orchestration and circuits. We therefore should widen our error message to include public variables that interact with secret variables.
Tasks
Describe the solution you'd like
Optional
Describe alternatives you've considered
We could do this for all public variables but this would limit the functionaltity that starlight can achieve.
Definition of done
When is this task complete?
The above tasks completed.