fix: allow OnConfigureHandlerReturn props to be null [EXT-2869]

[andipaetzold]

We currently get the following error when updating to app sdk v4 in a fresh CCA app

Type 'Promise<{ parameters: AppInstallationParameters; targetState: AppState | null; }>' is not assignable to type 'OnConfigureHandlerReturn'.
  Type 'Promise<{ parameters: AppInstallationParameters; targetState: AppState | null; }>' is not assignable to type 'Promise<{ parameters?: KeyValueMap | undefined; targetState?: AppState | undefined; }>'.
    Type '{ parameters: AppInstallationParameters; targetState: AppState | null; }' is not assignable to type '{ parameters?: KeyValueMap | undefined; targetState?: AppState | undefined; }'.
      Types of property 'targetState' are incompatible.
        Type 'AppState | null' is not assignable to type 'AppState | undefined'.
          Type 'null' is not assignable to type 'AppState | undefined'.  TS2322

    35 |     // invoked when a user attempts to install the app or update
    36 |     // its configuration.
  > 37 |     props.sdk.app.onConfigure(() => onConfigure());
       |                                     ^
    38 |   }, [props.sdk, onConfigure]);
    39 |
    40 |   useEffect(() => {

This PR allows null to be returned for parameters and targetState.

[colomolo]

Does it relate to previously done class->FC refactoring? Or the error comes from other place?

[andipaetzold]

Does it relate to previously done class->FC refactoring? Or the error comes from other place?

@colomolo The error occurs in the class-based and function-based CCA component. This wasn't introduced by our change.

[colomolo]

@colomolo The error occurs in the class-based and function-based CCA component. This wasn't introduced by our change.

Good, thanks!

[ghost]

🎉 This PR is included in version 4.0.0-alpha.24 🎉

The release is available on:

• v4.0.0-alpha.24
• GitHub release

Your semantic-release bot 📦🚀