You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starknet-foundry relies on Scarb's starknet-contract target to compile contracts that can be used during test runtime. There is a use case for foundry's users to create contracts only for this purpose. Such contracts could be defined either in test files, or under cfg(test) attribute. As of now, Scarb does not have any interface that would enable foundry to compile them.
cc @MaksymilianDemitraszek
The text was updated successfully, but these errors were encountered:
I think this could lead to smearing too much abilities everywhere. Why not just establishing a pattern to write contracts in separate packages and focus on implementing #717 instead?
Starknet-foundry relies on Scarb's
starknet-contract
target to compile contracts that can be used during test runtime. There is a use case for foundry's users to create contracts only for this purpose. Such contracts could be defined either in test files, or undercfg(test)
attribute. As of now, Scarb does not have any interface that would enable foundry to compile them.cc @MaksymilianDemitraszek
The text was updated successfully, but these errors were encountered: