FYI: existing type definitions
See original GitHub issueA while ago I contributed the @types/arcgis-rest-api type definitions to the DefinitelyTyped repository. If they meet your needs you could use these instead of creating them from scratch. (Available via NPM here)
I have another version with additional types, but that hasn’t been contributed yet. I’ve attached that version below, in case you want to use it. arcgis-rest-api.d.ts.zip
(The only reason that all of the types are in a single index.d.ts
file is simply because that’s the way the DefinitelyTyped project expects them to be.)
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
FYI, TypeScript definitions available · Issue #1723 - GitHub
I have created TypeScript definitions for jquery-handsontable, available here: ... FYI, TypeScript definitions available #1723.
Read more >How do I extend a TypeScript class definition in a separate ...
In the existing TypeScript definition file the objects are defined as classes rather than interfaces. e.g. declare module L { function circleMarker(latlng: ...
Read more >TypeScript: Adding Custom Type Definitions for Existing ...
Whether or not a library has type definitions is a big factor in deciding whether I'll use it. You can find the type...
Read more >FYI Updates (fyiup) - IETF Datatracker
The FYI Updates Working Group will oversee the work of updating two existing FYI documents. These documents are two that the
Read more >What is for your information (FYI) and how is it used?
Learn about the phrase for your information and its abbreviation, FYI. Explore FYI's history and how it is used. ... for your information...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK, wish I had done a quick google search on this before my previous comment. Turns out, If your package is written in TypeScript then you should publish the types w/ your package, so I’m going to PR @JeffJacobson’s types to arcgis-rest-common-types - at the very least the ones I’ll need for the new package for managing features. Also I talked IRL w/ @jgravois and he prefer’s the
I
prefix for interfaces, so I’ll add that to the ones I bring over.@JeffJacobson if we were to include all of your types (not just the ones we need), would that be something you’d be willing to use in your projects instead of
@types/arcgis-rest-api
, even if their prefixed w/I
? I think it’d be great if we could just maintain one package going forward. Hopefully it would be easier for you to publish here than over at DefinitelyTyped. Ultimately I’d like to deprecate the former and update it’s dependents.very cool! this is really similar to the
arcgis-rest-common-types
package we recently started stubbing out.we could certainly link out and promote your additional typings, but my first instinct is that it’d be good to combine forces. would you be interested in that?