-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Mocking internal package components #60
Comments
Hi @undsoft, might you provide more info, or maybe a code sample of the issue? TestBed.configureTestingModule({
imports: [MockModule(Package1Module), MockModule(Package2Module)],
declarations: [AnyComponentYouWantToTestComponent],
providers: []
}); |
Hi @undsoft, might you test the issue on 10.0.0-alpha.0 with the MockBuilder https://www.npmjs.com/package/ng-mocks/v/10.0.0-alpha.0#mockbuilder ? |
Hi @undsoft, have you tried beta version? 10.0.0-alpha.3 is the latest now. |
I'm closing the issue due to no feedback, feel free to reopen it if you meet any issues. |
Hi,
This may be two issues, but I'm trying to solve 1 problem.
Out project is split into several repos and they all consume modules from a core repo, which is build as an Angular package.
The problem is that this core repo only exposes modules, but not components.
Therefore I cannot do MockComponent(SomeComponent).
When I try to mock the whole module, I get weird errors like this:
I don't see anything special about this module. Some of the other modules can be mocked.
My suggestion would be to allow MockComponents to be created from selector.
The text was updated successfully, but these errors were encountered: