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
In Optimize, we make use of a number of extensions. We prefer to be explicit as to the order in which they are registered, as there are sometimes unfortunate dependencies between their responsibilities. It would be great if the EzeExtension could also be registered in such a way, so that we could give it an explicit @Order(x) too.
We also instantiate extensions differently depending on the type of test class (beforeAllMode vs beforeEachMode etc.). I can imagine us having some wrapper extension around the EZE extension that gives us similar behaviour. Access to the EZE extension as an instance field would also be useful for this.
The text was updated successfully, but these errors were encountered:
In Optimize, we make use of a number of extensions. We prefer to be explicit as to the order in which they are registered, as there are sometimes unfortunate dependencies between their responsibilities. It would be great if the EzeExtension could also be registered in such a way, so that we could give it an explicit
@Order(x)
too.We also instantiate extensions differently depending on the type of test class (beforeAllMode vs beforeEachMode etc.). I can imagine us having some wrapper extension around the EZE extension that gives us similar behaviour. Access to the EZE extension as an instance field would also be useful for this.
The text was updated successfully, but these errors were encountered: