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
Is there any way to call replaceBinds after the module has been initialized?
I'm coding a itegration test on a Modular App, and the moment the app initializes the flow keeps going, using the default modules (AppModule, AuthModule, finally CashierModule).
But they come in order, the last step is the CashierModule, which initialized his own module after the QR scanner has been completed.
If i try to initModule(CashierModule(), replaceBinds: [mockedBind]), it seems that the app will create a new instance of this module (not tested) when the moment arrives. But i think this is expected.
But when i try to initModule after the default cashier module has been initialized by the app integration flow, it seems to have no effect replacing the desired bind
The text was updated successfully, but these errors were encountered:
cl0v
added
new
New issue request attention
question
Questions about using some feature or general working of the package
labels
Oct 19, 2023
I'm trying to use Modular.replaceInstance(dioMock); as shown in https://modular.flutterando.com.br/docs/flutter_modular/test/#injection-test but it seems that Modular removed this static method... Error: The method 'replaceInstance' isn't defined for the type 'IModularBase'. Try correcting the name to the name of an existing method, or defining a method named 'replaceInstance'
Is there any way to call replaceBinds after the module has been initialized?
I'm coding a itegration test on a Modular App, and the moment the app initializes the flow keeps going, using the default modules (AppModule, AuthModule, finally CashierModule).
But they come in order, the last step is the CashierModule, which initialized his own module after the QR scanner has been completed.
If i try to initModule(CashierModule(), replaceBinds: [mockedBind]), it seems that the app will create a new instance of this module (not tested) when the moment arrives. But i think this is expected.
But when i try to initModule after the default cashier module has been initialized by the app integration flow, it seems to have no effect replacing the desired bind
The text was updated successfully, but these errors were encountered: