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
FWIW, I have the same problem in one Angular app, but not in another. I found that in the app where the problem occurs, the decorator assigns the BlockUI instance to the component's prototype but the component object has its own property with an "undefined" value.
In the app where everything works, the BlockUI instance is still set into the prototype but the component object itself doesn't have the property and is getting the prototype value.
I'm upgrading to angular 18 from angular 17 in one of my projects and i'm getting error where using
@BlockUI()blockUI!: NgBlockUI
gives error:
TypeError: Cannot read properties of undefined (reading 'start')
had to switch to using the BlockUIService instead and specifying name in selector like so:
`<block-ui [template]="foregroundSpinner" name="test" >
constructor(
private blockUI: BlockUIService
){
this.blockUI.start('test')
`
The text was updated successfully, but these errors were encountered: