Discuss: Replace implicit return type with explicit and void return?

[danielsogl]

Discuss: Replace implicit return type with explicit and void return?

[ihadeed]

That would make the definitions a lot cleaner.

Wouldn't it also help if we ensure that every promise has a defined type
--example, like in geolocation.ts : Promise<Geoposition>, instead of
Promise<any> ? I think it will help the docs generation process as well.

[tlancina]

Yeah I think if possible we should try and have the wrapper be as small as possible, and use interfaces for the option objects as well:

  /**
   * Show the ActionSheet.
   */
@Cordova()
  static show(options?: ActionSheetOptions) : Promise<any> { return }

  /**
   * Hide the ActionSheet.
   */
  @Cordova()
  static hide() : Promise<any> { return }

I also am not a huge fan of having the interfaces cluttering up the top of the files, it would be nice to have just the description of the wrapper, with the very concise method definitions. I can't remember if there is a good way to move them into their own files, while still using declaration: true. I want to say we have to concatenate them manually as part of the build.

Regarding the promises, I agree, if possible they should all have the correct type.

[ihadeed]

Is it something like this that you're looking for : https://www.npmjs.com/package/declaration-bundler-webpack-plugin ?