Martín Triay

> * Avoid adding messages to assertions as much as possible to avoid redundancy. Is this really wanted? Won't we lose the error message when the test fails? Because that's...

In tests, we should perform checks/asserts right after state changes/calls/queries, instead of performing several of them an asserting later. For example: ```cairo let bar = contract.bar(args..); assert!(bar); let foo =...

@TomasDePomas 's solution worked for me!

Sorry for the late response. I think I've seen this before and it was an `snforge` issue. Could you work around it? It should work fine with newer versions.

thanks! we'll reconsider after releasing

> For example, say I want to use only access control and reentrancy guard When OZ modules depend on each other, would this require the user to add "OZ dependencies"...

@Bal7hazar i think the best is to wait for components to streamline this eventual separation. although not a blocker, another feature that'd help here is supertraits (or similar) to extend...

@Bal7hazar sorry for the long silence. are you still willing to work on this?

Great! That'd be a useful reference. We're still going to add this to our library, I expect us to work tackle it sometime during Q1 2024. Anyone interested in tackling...

Closing this since it will not be relevant anymore after the ongoing Cairo 1.0 migration. If you think this is a mistake, feel free to open a new issue.