feat(test): add withProviders for per test providers#5891
Conversation
|
please rebase |
|
This is pending my fixing and resubmitting #5819 I'll update when it's ready to go. |
c19ce2e to
6783f35
Compare
|
This is now unblocked and rebased. |
8f5a717 to
295e6e7
Compare
|
This is now actually passing Travis - typing issues fixed. |
295e6e7 to
3554c91
Compare
|
@IgorMinar could you take another look at this? All rebased and passing. |
|
Prodding @IgorMinar |
|
Further prodding @IgorMinar Is anyone available to review? |
3554c91 to
caf940a
Compare
|
@btford would you be able to review? |
There was a problem hiding this comment.
opinion nit: If we're worried about perf here, I think this check fits better in addProviders, but up to you whether to update.
There was a problem hiding this comment.
I don't think perf should be an issue here, it's certainly not a hot code path.
There was a problem hiding this comment.
In that case, I'd vote removing the check altogether and collapsing these 4 lines into 1.
There was a problem hiding this comment.
Actually, we do need the check here - we don't want to call addProviders at all if there's no new ones, to avoid throwing an error if we've already instantiated the injector.
|
LGTM |
|
Thanks! |
caf940a to
9c0a59e
Compare
|
Landed as c1a0af5 |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Closes #5128