HookMatchCriteria compile error in TypeScript with strict null checks about core

[christopherthielen]

New core and angularjs releases tonight

[helmutschneider]

@christopherthielen Not sure why this was closed - the issue still exists in the current code:

export interface HookMatchCriteria {
  [key: string]: HookMatchCriterion;
  to?: HookMatchCriterion | undefined;
  from?: HookMatchCriterion | undefined;
  exiting?: HookMatchCriterion | undefined;
  retained?: HookMatchCriterion | undefined;
  entering?: HookMatchCriterion | undefined;
}

[key: string]: HookMatchCriterion is typed as non-undefined which causes the compilation to fail on all the optional properties. The code should probably read:

export interface HookMatchCriteria {
    [key: string]: HookMatchCriterion | undefined;
    to?: HookMatchCriterion;
    from?: HookMatchCriterion;
    exiting?: HookMatchCriterion;
    retained?: HookMatchCriterion;
    entering?: HookMatchCriterion;
}

[gaui]

When is 0ae585e going to be released? I added that patch and everything compiles.

[mrahhal]

Also still facing this.

[AnimaLupi]

Same issue here.

EDIT: Investigating atm as I'm probably on an older version due to compatibility with the rest of the app.

EDIT2: It seems to be an issue even with latest ui-router/core 5.0.4.

[mrahhal]

Right now this is the only blocker for me to use the "strict" option. A bit frustrating.

[gaui]

Chris 🙏