Leonard Brünings
Leonard Brünings
What is the use-case? And shouldn't we have something that is stable across invocations, otherwise it's use is severely limited.
With the current code you could easily externalize it to a helper function. I don't see a strong reason to add it to the API and only see potential problems...
Given that we now have the extension store, do you still see a need? IMHO, it is too niche to be added to spock-core.
> I would, however, like to keep this as low-profile as possible. I've been considering for a while to introduce something like https://junit-pioneer.org/ for Spock extensions. Where they can live...
> That does not answer my questions. But if you like to get feedback on that idea: It would scare me off. I dislike long-winded, tedious processes with lots of...
Thank you for the update, the new implementation goes in the right direction, the only thing I'm still not convinced about is the `executionOrder` on the `SpecInfo` together with the...
@ceki Apart from the merge conflict, are there any reasons why this should not be included? If not I would fix the commit so that it can be merged.
Adding a mockito mock factory would relate to #1220, which would create the infrastructure to add additional mock factories. We would also need to think about a better way to...
It has evolved nicely. I'm still thinking about how we could make it extensible in a meaningful way. I think we've discussed making it possible to change the operation with...
Block listener support will be implemented via #1575