Presubmit.

I had encountered an issue with TS 4 and 10.1 which was reported here, which is still happening with 11.0.0-rc.0 and TS 4.

ERROR in src/app/some/some.component.ts:26:81 - error TS2729: Property 'some_id' is used before its initialization.

26   public data: any = {some_id: this?.some_id, date: new Date()};
                                                                                   ~~~~~~~~~~~~~~~

  src/app/some/some.component.ts:22:12
    22   @Input() some_id
                  ~~~~~~~~~~~~~~~
    'some_id' is declared here.

As it is evident, the variable is defined before its being used.
Also it works fine with 3.9.
I'm not sure if TS 4.0 introduced something that could cause this issue, but i think its ng so just wanted to confirm. I tried to look into issue tracker for similar reports, though not that deeply, but didn't found any.

@KapilSachdev, could you please create a new ticket and provide the necessary information (by following the template), so that the team can have a look? As a part of the new ticket, please also provide an example of the code that doesn't work, so that we can reproduce the problem. Thank you.

Before creating a new issue i wanted to confirm one more thing, in case the behaviour is expected.
When the properties are being called on component initialization the issue occurs with TS 4 but not with TS 3.9.

@Input() some_id
public data: any = {some_id: this?.some_id, date: new Date()};

ngOnInit() {
}

Moving the data property initialization that uses @Input() property inside ngOnInit fixes the problem in TS 4

@Input() some_id

ngOnInit() {
  public data: any = {some_id: this?.some_id, date: new Date()};
}

Is this expected behaviour because @Input is not yet passed to the component? In case yes, why it does nto happens with TS 3.9

@KapilSachdev I don't think your use-case is specific to Angular (the error is being produced by the TypeScript). You can see how different version of TypeScript handle this in TypeScript Playground.

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.}