Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
From: Mike Hartington <mikehartington@gmail.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_5117FFF4-3927-4650-9DFA-C6572165C73A"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [DISCUSS] Include TypeScript definitions in plugins
Date: Mon, 9 Jan 2017 17:40:47 -0500
References: <216DC1F8-58A7-4E66-906B-C2CB5BD37F15@microsoft.com>
 <CAE6O_-Z3hGK-ZiKA4mT5qzj3RQjGpzeTtttUq3pEz9t-ydOXTA@mail.gmail.com>
 <CANDRhHA-umqOZZZ+FtWEVbxn3wR2dBcqHN7fVgZkpR_agsA3FA@mail.gmail.com>
To: dev@cordova.apache.org
In-Reply-To: <CANDRhHA-umqOZZZ+FtWEVbxn3wR2dBcqHN7fVgZkpR_agsA3FA@mail.gmail.com>
Message-Id: <50225F9F-E23B-4EF9-8703-34772BA99EC1@gmail.com>
archived-at: Mon, 09 Jan 2017 22:40:56 -0000

--Apple-Mail=_5117FFF4-3927-4650-9DFA-C6572165C73A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Types can be in sub-folder.
As long as the type entried just points to the path

=
https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.=
html =
<https://www.typescriptlang.org/docs/handbook/declaration-files/publishing=
.html>


Mike Hartington


> On Jan 9, 2017, at 5:38 PM, Victor Sosa <sosah.victor@gmail.com> =
wrote:
>=20
> +1... I love this idea! Will help a lot to static analysis tools and =
IDEs.
>=20
> On Mon, Jan 9, 2017 at 3:56 PM Shazron <shazron@gmail.com> wrote:
>=20
>> 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)
>>=20
>> On Mon, Jan 9, 2017 at 5:23 AM, Vladimir Kotikov (Akvelon) <
>> v-vlkoti@microsoft.com> wrote:
>>=20
>>> Hey, everybody!
>>>=20
>>> I=E2=80=99d 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.
>>>=20
>>> 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).
>>>=20
>>> 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
>>>=20
>>> Does anyone have any considerations/objections about this proposal?
>>>=20
>>> -
>>> [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
>>>=20
>>> -
>>> Best regards, Vladimir
>>>=20
>>>=20
>>>=20
>>> -
>>> Best regards, Vladimir
>>>=20
>>>=20
>>>=20
>>=20


--Apple-Mail=_5117FFF4-3927-4650-9DFA-C6572165C73A--