Don't provide a service when the getter throws an error #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the case where I have an external service which may not be ready (say it has to be loaded asynchronously), I want to throw an error:
The present behaviour, on getting
container.asyncService
will throw the error once, and then afterwards returnundefined
. Even if the service resolves at some point, the result ofcontainer.asyncService
will always beundefined
after the initial call.This changes the behaviour so as to throw the error until the service resolves, and then behave as before. The use case is that I have services dependent on another service which is not ready until after
bottle.resolve()
has been called. I want to fail fast if anything tries to access that service before then.It's a super-simple change in the code which just involves changing the order of when property names are deleted from the container vs when
$get
is called.