-
-
Notifications
You must be signed in to change notification settings - Fork 19
Table layout #146
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
Draft
dhilt
wants to merge
12
commits into
master
Choose a base branch
from
table-layout
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Table layout #146
Changes from 6 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
228296c
table layout dev
dhilt e38ad82
Remove intermediate <div ui-scroll> wrapping tag for ui-scroll component
markdBC aa0b8b4
Merge pull request #145 from markdBC/table-layout
dhilt 852f072
Merge branch 'master' into table-layout
dhilt 928a285
ng-template fix
dhilt 12222ad
pass parent element from directive + ngOnInit fake call
dhilt 86be8e4
Explicitly invoke change detection after dynamically creating compone…
markdBC cd6232d
Merge pull request #147 from markdBC/table-layout
dhilt 467a7e2
delayed change detection: the workflow must be initialized after firs…
dhilt 15bd614
Merge branch 'master' into table-layout
dhilt e086b97
Merge branch 'master' into table-layout
dhilt d455c33
Merge branch 'master' of github.com:dhilt/ngx-ui-scroll into table-la…
dhilt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markdBC To say I don't like this would be a considerable understatement... ngOnInit must be invoked implicitly, and I have no idea why it became broken. It has something to do with new approach of creating the component on the directive level. The demo we developed on stackblitz has the same issue.
It would be very nice if you could take a look and help with it. For testing in ngx-ui-scroll environment you may use http://localhost:4200/#/test (after npm start), which runs demo/app/samples/test.component.html template. There are multiple issues behind this one, so to see the result is still impossible, but the initialization could be handeled in a proper way
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dhilt The problem is that
ngOnInit
is called after the first timengOnChanges
is called (https://angular.io/guide/lifecycle-hooks#lifecycle-sequence).However, while
ViewContainerRef.createComponent
causes an invocation ofngOnChanges
, the same is not true forComponentRef.create
.You can find the definition of
ViewContainerRef.createComponent
, atpackages/core/src/view/refs.ts:180
of the Angular source code:ViewContainerRef.createComponent
calls theComponentRef.create
method, and then callsViewContainerRef.insert
, which among other things causes change detection to occur inside the component.A solution is to explicitly invoke change detection for the component, via
ComponentRef.changeDetectorRef.detectChanges()
. This is probably only slightly better than explicitly invokingngOnInit
, but at least we're not calling a lifecycle hook directly.I've made a PR with this change at #147 and have a StackBlitz demo at https://stackblitz.com/edit/table-implicit-lifecycle-hook-invocation.