-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async before and after #953
Comments
Hi @LMnet , in 3.0 we have made BeforeAndAfter and BeforeAndAfterAll to work with async style trait, I wonder if they fit your use case? |
I'm using 3.0 version with |
@LMnet That's done here: The withAfterEffect method registers the afterAll code to run as an effect after the Status returned by super.run completes. The Status is kind of like a Future[Boolean]. |
@bvenners But what about |
Is this issue solved already ? I put up a related SOF question: |
What exactly the solution for this ticket? I have requirements, where we need to call multiple future calls in the beforeAll method. |
We haven't done anything with beforeAll. Let me think about if that is possible, and if so how best to go about it. |
What's the status of this issue? |
I am also in need of an async beforeAll. Have not found any solution which does not include blocking (which is not possible in Scala.js). |
Hi there! Is this issue already solved? I am also interested in it for Scala in JVM |
How is this issue closed? Even if there's a workaround for an asynchronous Should I open a new issue? |
Please reopen this issue as there is no possibility to execute asynchronous code in |
It is more feature request, than issue.
ATM all
before
andafter
stuff is fully synchronous: all methods returnsUnit
. It would be good to have a possibility to have an asynchronous versions of this methods. Typical use case for this async methods: operations with DB. For now i'm forced to useAwait.ready
to block my async operations.I can suggest two options for the implementation:
BeforeAndAfterAllAsync
.Personally, I prefer the first way.
The text was updated successfully, but these errors were encountered: