gr2m / javascript-plugin-architecture-with-typescript-definitions

Plugin architecture example with full TypeScript support

Repository from Github https://github.comgr2m/javascript-plugin-architecture-with-typescript-definitionsRepository from Github https://github.comgr2m/javascript-plugin-architecture-with-typescript-definitions

Remove required `version` option, implement required constructor options dynamically based on `Base.Options` interface

gr2m opened this issue ยท comments

This is a follow up to #57 (comment)

I think what I'd suggest we do is to add a new use-cases folder, and in that folder create required-options with index.js, index.d.ts and index.test-d.ts files.

In /use-cases/required-options/index.d.ts we would define a required option by extending the Base.Options interface and then add tests to index.test-d.ts to make sure the types work correctly with the new Base(options) constructor and with .defaults(options) calls

๐ŸŽ‰ This issue has been resolved in version 3.4.0 ๐ŸŽ‰

The release is available on:

Your semantic-release bot ๐Ÿ“ฆ๐Ÿš€