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
Currently, if we have a file pool.rs (imported as a module in lib.rs) that contains a blueprint module pool, and inside it the Pool blueprint, the way to get the test bindings would be:
use pool::test_bindings
Wouldn't it be better that test_bindings was placed at the blueprint module level, instead of the file module level? So it would be:
use pool::pool::test_bindings
This would enable the user to create more than one blueprint in the same file, if for any reason it is wanted.
The text was updated successfully, but these errors were encountered:
Hi @gunther9, your recommendation makes sense to me especially when thinking about having multiple blueprints in a single file, this is something that we support that all other parts of the stack so supporting/enabling it with scrypto-test makes sense. There is also another alternative where the test_bindings module could be prefixed with the blueprint name. So, for Radiswap the test bindingas module could be radiswap_test_bindings.
Currently, if we have a file
pool.rs
(imported as a module in lib.rs) that contains a blueprint modulepool
, and inside it the Pool blueprint, the way to get the test bindings would be:use pool::test_bindings
Wouldn't it be better that test_bindings was placed at the blueprint module level, instead of the file module level? So it would be:
use pool::pool::test_bindings
This would enable the user to create more than one blueprint in the same file, if for any reason it is wanted.
The text was updated successfully, but these errors were encountered: