+1... I love this idea! Will help a lot to static analysis tools and IDEs. On Mon, Jan 9, 2017 at 3:56 PM Shazron <shaz...@gmail.com> wrote:
> Thanks for bringing this up Vladimir, > +1 -- but does the .ts definition need to be in the root? I'd rather it be > in a subfolder (either an existing one like 'www' or a new one) > > On Mon, Jan 9, 2017 at 5:23 AM, Vladimir Kotikov (Akvelon) < > v-vlk...@microsoft.com> wrote: > > > Hey, everybody! > > > > I’d like to propose/discuss the idea of redistributing Typescript > > definitions along with core plugins, so that users who write their apps > in > > Typescript would get the typings in their projects without additional > mess > > with 'tsd'/'typings' (these all are the package managers for typescript > > declarations) or manual installation from '@types' NPM org. > > > > As mentioned above, our main goal - to reduce the number of additional > > actions needed to either add the plugin to Typescript project or get the > > types information and intellisense for JavaScript projects. Also, this > > would reduce the number of network calls to other services (typings > > registry, NPM registry) which are known as common points of denial (per > > telemetry data). > > > > The changes are pretty minimal and include adding a d.ts file with type > > definitions (taken from DefinitelyTyped[1]) and 'types' entry to > > package.json according to Typescript convention [2]. The sample > > implementation for camera plugin is here: https://github.com/apache/ > > cordova-plugin-camera/compare/master...vladimir-kotikov:add-typings > > > > Does anyone have any considerations/objections about this proposal? > > > > - > > [1] https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/ > > cordova-plugin-camera/index.d.ts > > [2] http://www.typescriptlang.org/docs/handbook/declaration- > > files/publishing.html > > > > - > > Best regards, Vladimir > > > > > > > > - > > Best regards, Vladimir > > > > > > >
