You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
template type-checking in Ivy throws error for slice pipe #30086
@chacabuk SlicePipe is now more strictly typed and can catch errors with Ivy and fullTemplateTypeCheck that it couldn't previously. If you think this is a bug in Angular, and not an real error in your template, please open an issue with a reproduction, and we'll take a look.
@daileytj The issue should be fixed in Angular 8.0.0, so if you still encounter it in recent versions, please open an issue with a minimal reproduction and ping me, and I or someone on the team will take a look.
angular-automatic-lock-bot commented on Sep 15, 2019
Activity
cexbrayat commentedon Apr 25, 2019
Should be fixed by 79141f4 which will be available in
8.0.0-rc.0. I'll reopen if that's not the case.chacabuk commentedon Jun 3, 2019
Angular CLI: 8.0.1 Still broken.
Property 'name' does not exist on type "<T>".slice_pipe.ts line 65:
transform<T>(value: ReadonlyArray<T>, start: number, end?: number): Array<T>;cexbrayat commentedon Jun 4, 2019
@chacabuk SlicePipe is now more strictly typed and can catch errors with Ivy and fullTemplateTypeCheck that it couldn't previously. If you think this is a bug in Angular, and not an real error in your template, please open an issue with a reproduction, and we'll take a look.
daileytj commentedon Jul 19, 2019
I'm having this same issue. Has anyone been able to find a workaround and/or is this issue being addressed by the Angular team?
cexbrayat commentedon Jul 20, 2019
@daileytj The issue should be fixed in Angular 8.0.0, so if you still encounter it in recent versions, please open an issue with a minimal reproduction and ping me, and I or someone on the team will take a look.
angular-automatic-lock-bot commentedon Sep 15, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.