-
Notifications
You must be signed in to change notification settings - Fork 490
Conversation
Nice! 👍 Some suggestion: I noticed we don't have any CI on the demo project. We should add another Github action workflow to run the tests on the demo project. I tried to run the tests in local and I got some errors:
I'm not sure what I'm missing... |
@l-lin that's what I'm planning on doing next. I'll create the workflow after we merge this PR. Could you try deleting Also, in order to merge this PR, I need to create a test case for NgTemplateRef which is currently in a race condition as explained above. This involves adding support for |
👌
Indeed, the
Since it looks like some change in the library code, it would be best to update in another PR. |
a5bfd08
to
1be05c3
Compare
- extends from `tsconfig.json` - fix esModuleInterop flag error
1be05c3
to
b633d5b
Compare
- send dtOptions to trigger event - add unit tests
@l-lin please check if the unit tests passed and the unit test itself is suitable for the component(s). Finally, I can see the finish line on this. |
issue: Some tests are not passing:
|
@l-lin Do you know of a way to reproduce this issue so that I can investigate it? |
This is what I did: cd /path/to/demo
rm package-lock.json && npm i --force && CHROME_BIN=/snap/bin/chromium npm test Maybe you can push your package-lock.json? |
- part 2 of d6fbd0b
Here you go: |
Mmh, I still got the error, so it's not the |
I'm opening this PR as continuation to #1529 I couldn't re-open my previous PR so here we go again!
Features:
Provides unit tests for following entities:
[ x ] Basic examples
[ x ] Advanced examples
Unit test for NgTemplateRef component isn't working due to a race condition with
dtOptions
Input
binding on the directive anddtTrigger
inside component'sngAfterViewInit
.I might cover unit tests for Extensions examples in a future PR but this takes precendence.
Closes #1513