It is mostly for convenience.
-
debug profile - name TBD
TODO: debug profile should have all the things debugger needs turned on by default (e.g. skip-optimizations = true). We can make it a default profile used by snforge test --launch-debugger - mind that it would require changes in debug lenses logic in LS. Feel free to create appropriate follow-up tasks after taking on this issue.
Effect: better UX when using debugger.
-
test profile
TODO:test profile should have the same settings as dev but with sierra-replace-ids = false. It would serve the same function as in Cargo. Then we can make test targets in scarb respect sierra-replace-ids - currently it has it hardcoded to false. Rationale for hardcoding it to false was that tests in projects such as garaga would crash with OOM if sierra-replace-ids = true was respected (which is the default for dev profile).
Effect: better devX for cairo-debugger developers (ability to obtain human readable sierra in tests)
It is mostly for convenience.
debugprofile - name TBDTODO:
debugprofile should have all the things debugger needs turned on by default (e.g.skip-optimizations = true). We can make it a default profile used bysnforge test --launch-debugger- mind that it would require changes in debug lenses logic in LS. Feel free to create appropriate follow-up tasks after taking on this issue.Effect: better UX when using debugger.
testprofileTODO:
testprofile should have the same settings asdevbut withsierra-replace-ids = false. It would serve the same function as in Cargo. Then we can make test targets in scarb respectsierra-replace-ids- currently it has it hardcoded tofalse. Rationale for hardcoding it tofalsewas that tests in projects such as garaga would crash with OOM ifsierra-replace-ids = truewas respected (which is the default fordevprofile).Effect: better devX for
cairo-debuggerdevelopers (ability to obtain human readable sierra in tests)