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.
Example of allowing the container code author to selectively inject a runtime-level superpower into a datastore that's willing to take it. dispose() isn't the best example since the container code author probably shouldn't even be calling it anyway, but it's funny :). Imagine I'm calling getAudience() or something instead.
Alternatives might include leaving the factory alone but having the datastore's entryPoint be a creator function, i.e. entryPoint of
{ createRiskyDiceRoller: (disposeContainer: () => void): IDiceRoller }
and then have the container code's entry point complete the creation aftergetDataStoreEntryPoint
and before returning its entryPoint. But here I'm confident that the RiskyDiceRoller won't use before initialize so I just pass it directly.