* (d3-geo): Update to 1.3.1 and JSDoc
* [Chore] Updated definitions to conform to version 1.3.1
* [Feature] Added `geoIdentity()` and removed `geoClipExtent()`
* [Feature ] Added geoGraticule10()
* [Update] Changed API for `geoPath(...)`
* [Enhancement] Complete overhaul of JSDoc comments
* [Chore] Some changes to sequencing of definitions
* [Fix]: Fixed GeoPath pointRadius() Accessor (getter may return constant number or accessor function.
* [Fix] GeoPath generator may return string (SVG path string) or undefined (when called with rendering context)
*
* (d3-geo) Test Updates
* Add test for `geoGraticule10()`
* Remove tests for `geoClipExtent()`
* Add tests for `geoIdentity()`
* Fixed clipExtent tests to include explicit union with `null` type for return value of getter
* Fixed pointRadius getter test on geoPath to allow for accessor or number to be returned by getter
* (d3-geo) Tests Additional
* Add some more tests for new geoPath(...) API
add following options to the bootstrap-datepicker/DatepickerOptions. Also update the options url to point to the correct URL.
templates?: any;
zIndexOffset?: number;
showOnFocus?: boolean;
immediateUpdates?: boolean;
title?: string;
* Cleanup Imports
These should be uniform, and should all use the require() syntax, as
they’re referring to common js modules.
* Enable client.calls.list()
* Split up RestMethod signature
By splitting up the union into an overload, we get much more useful
autocomplete info.
* Remove BaseRequestCallback
BaseRequestCallback was only used in RestMethod, and it’s incorrect:
the user’s callback is always called with 3 arguments. I think this was
an attempt to say that the user’s callback doesn’t need to specify a
third argument, but a two-argument callback will already conform to
RequestCallback anyway.
As the updated tests show, this change gives us better type inference too.
* Use new Node HTTP Interface
This MiddlewareFunction type isn’t assignable to an express middleware
otherwise, as the latest express-static-core type declarations removes
Http.ServerRequest from the type definition of an express RequestHandler
The documentation is pretty bad, but Relay's getFragment method allows for an optional second argument for passing initial variables to the fragment. This simply adds that.
* Remove global pollution to allow Node.JS and Leadfoot to be included together (Leadfoot uses a part of Dojo but not the conflicting globals). Add Thenable to support Leadfoot typings.
* Add leadfoot typings and initial tests.
* Remove ... references from tsconfig
* added @types for N3, an RDF package
* changed file names to match requirements for syncing with @types
* naming recommendation conformance
* added type definitions for webgme
* provide constructor and factory with same function name
* checkpoint
* removing declare module n3, making ProperModule
* changed reference path to types and corrected errors associated with strict null
* checkpoint
* test the project with "tsc --project tsconfig.json"
* changed from "reference path=" to "reference types=" when possible
* removing wildcard declaration
* combined *.d.ts files and *-tests.ts
* removed task completion comments
* removed patch version and strict null check on
* Initial commit for code v4.0.0
* Merge upstream, remove module declaration
* Fix include alias signature, fix typos
* Add stronger types to tests and run linter
Tom Wanzek