add trigger of ngOnChanges on scrollUp distance changes #375
+3 −2
Conversation
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
Fix the default throttle
Implement infiniteScrollDisabled property (Issue 17)
fix build script error
Use opencollective-postinstall instead of opencollective
[7.1.0]: Release
fixes the scrolling in the window container
* Update to Angular 8 * Update example, readme and changelog * Adjust typescript version, delete unnecessary dependency from example
There are a few known scenarios where the opencollective postinstall npm script can cause things to break further down the pipeline - a few being 'certain build/CI environments', 'script permission issues' and 'offline installs'.... Arguably, displaying a banner soliciting funding shouldn't disrupt the development or build processes of projects leveraging libraries that are optionally, and non-functionally, using opencollective. Ultimately, at the heart of the failure, is a non 0 exit code being returned in the cases that opencollective fails to properly execute. To prevent this non-zero exit code failure so that subsequent npm processes aren't disrupted as a result of non-functional dependency issues, a "|| exit 0" should be added to the postinstall npm script. There are many discussions about this issue and workaround - here are a few: opencollective/opencollective-cli#5 nuxt/nuxt#1357 opencollective/opencollective-cli#3 opencollective/opencollective-postinstall#2 compodoc/compodoc@99ea09f
* feat: update to angular 9 (orizens#351) * feat: make example app work
* feat: update angular to 10.x * chore: update angular to 10.x in examples dir
Owner
| checks are failing. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
20 participants
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.
fix conflicts fromPR:225