-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Issues with ChildContent
using attribute selector
#445
Comments
Thanks for the report! About beer, thanks, it would be nice. The next task is to configure patreon 🤣 |
ChildContent
using attribute selector`ChildContent
using attribute selector
Hi there, Might I ask whether When I was testing it, for me it works only when id is provided: Another thing is that such mock components require Working on the fix to avoid failures in tests. |
NVM, this explains a lot of things actually 😅 |
Yeah, but please wait with closing it. I added a fix to avoid runtime failures in such cases. |
fix: skipping wrong query selectors #445
v11.11.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems. |
Hi @GerkinDev, how is life? I hope everything is fine on your side. It took a while, and finally I've finished the process of verification and can officially accept beer donations: https://github.com/sponsors/satanTime. |
Hey there ! Finally ! So, it ain't that much, but I will for sure back you much more when the fundraising of my company is done :) for now, I'm quite low on money. Take a beer, you deserve it ;) |
Thanks for the beer! It is a lot, even 1/10 would be enough :) Good luck with the business and stay in touch 🤜 🤛 . |
So, it's me again. I'm having problems to mock component using
ContentChild
selected by attribute. Here is the demo: https://stackblitz.com/edit/ng-mocks-examples-mp9pgs?file=app/app.spec.tsRelated to #68
Thank you so much for your work. And, do you have a patreon or something so that I can buy you a beer ? 🍻
The text was updated successfully, but these errors were encountered: