ui-pager
ui-pager copied to clipboard
ERROR: `isListLikeIterable()` is not a function in @nativescript/angular
With these versions installed:
@nativescript-community/[email protected]
@nativescript/[email protected]
@angular/[email protected]
I get the following error when I run my app:
ERROR Error: Uncaught (in promise): TypeError: (0 , _nativescript_angular__WEBPACK_IMPORTED_MODULE_0__.isListLikeIterable) is not a function
TypeError: (0 , _nativescript_angular__WEBPACK_IMPORTED_MODULE_0__.isListLikeIterable) is not a function
at set items [as items] (file: src/webpack:/mandy/node_modules/@nativescript-community/ui-pager/angular/fesm2022/nativescript-community-ui-pager-angular.mjs:47:61)
at setInputsForProperty (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:13333:0)
at elementPropertyInternal (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:12496:0)
at Module.ɵɵproperty (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:15175:0)
at ImageCarouselComponent_Template (file: src/webpack:/mandy/src/app/features/thread/image-carousel.component.ts:32:21)
at executeTemplate (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:12113:0)
at refreshView (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:11998:0)
at refreshComponent (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:13072:0)
at refreshChildComponents (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:11788:0)
at refreshView (file: src/webpack:/mandy/node_modules/@angular/core/fesm2015/core.mjs:12048:0)
ERROR TypeError: Cannot set properties of undefined (setting 'selectedIndex')
I already found https://github.com/nativescript-community/ui-pager/issues/34 and https://github.com/nativescript-community/ui-pager/pull/35 which seems to solve a similar issue, but it seems to have no effect on the deprecated function that is causing issues now.
Is this a known issue? Will there be a fix for current Angular versions?
I think you'll have to bump to Angular 16+ or roll back this plugin. For me, sticking to Angular 16 and [email protected] works fine 👍🏻
@guillemc23: your comment saved me today. thank you! but it is kind of strange that we have to specify versions that hard. Does not really fit into semantic versioning from my perspective.