5.3.11 breaks Angular components using classes defined further in code

[kausters]

Describe the bug
After upgrading from SB 5.3.10 to 5.3.12 my Angular 9 components started failing with an error: "Cannot access 'DropdownListItem' before initialization"

I found that the problem occured when I had a component that used this DropdownListItem but the DropdownListItem itself was defined in that same file, after the original class. Moving DropdownListItem to the top of the file solved the issue but that's not how we want to build our components.

So something like this (truncated):

@Component({
    selector: 'app-dropdown-list',
    templateUrl: './dropdown-list.component.html',
    styleUrls: ['./dropdown-list.component.scss']
})
export class DropdownListComponent implements OnInit {
    @Input() listItems: DropdownListItem[]

    constructor() {}

    ngOnInit() {}
}

export class DropdownListItem {
    public name: string
    public value: string | number

    constructor(name: string, value: string | number) {
        this.name = name
        this.value = value
    }
}

I found two things connected with this problem:

1. Angular: Emit decorator metadata by default #9701 added emitDecoratorMetadata: true to TS compiler options
2. ES2015 + emitDecoratorMetadata causes Cannot access before intialization angular/angular-cli#15077 that option on Angular causes the error I encountered

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[aloulouamine]

Hi,

Got the same issue. Is there a workaround to this issue ?

thx

[kausters]

Not that I know of. My company has frozen the Storybook version but that's it.

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[stale]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!