* `node-fetch`: add test for `Headers.raw`
* `node-fetch`: `Headers.raw`: add `string[]` to index signature value type
* `node-fetch`: `Headers.raw`: add `undefined` to index signature value type
* `node-fetch`: enable `strictNullChecks` and fix errors
* Revert "`node-fetch`: `Headers.raw`: add `undefined` to index signature value type"
This reverts commit 15ad14d72c42fa1f3ba472bc15f38a88230f3a4f.
* Fix expect type format
* Remove string
For `unclick` the handler argument was already marked as optional. As in snapsvg's [implementation of the `un...` methods](https://github.com/adobe-webplatform/Snap.svg/blob/master/src/mouse.js#L340) there is no difference in how the various events are handled, the handler should also be optional for the other event types. I tried this with `undblclick` in particular, and it works as expected (removes all `dblclick` events).
* fix: let jQuery's insertAfter / insertBefore accept JQuery<HTMLElement> as well as HTMLElement
* jquery now requires typescript 2.4
* fix jQuery dts to compile on TypeScript 2.3
* Use correct type for GatewayDestProps component
* Test react-gateway GatewayDest component prop type
* Add another test for react-gateway GatewayDest component prop type
* [numeral] Remove method that no longer exists
This method was removed in adamwdraper/Numeral-js@f8f2696, and it
was changed in adamwdraper/Numeral-js#398 from a dedicated method
to using `$` in the format.
* [numeral] Fix tests
* Fix mathjs Unit type definitions.
- Remove Unit class methods from the Unit instance interface.
- Add some missing Unit instance methods referenced in the mathjs docs.
One notable problem this resolves is that mathjs types were not
importable in Node without the DOM library due to the Unit.parse
signature referring to DOMStringList.
* Array -> ReadonlyArray in splitUnit() signature.
* update typing
- add missing event handlers from https://github.com/plotly/react-plotly.js/#event-handler-props
- add addFrames / deleteFrames functions
- use Font interface in ScatterMarker.colorbar
- change Font.color type from string to Color
- fix 'common mistakes': tabs to spaces
* fix linting errors
* use tab indentation and require in tslint
* Updating Matrix class to match 11.5 documentation and implementation.
* Updating Point class to reflect 11.5 documentation and implementation.
* Updating Rectangle class to reflect 11.5 documentation and implementation.
* Updating Size class to reflect 11.5 documentation and implementation.
* Updating PaperScope class to reflect 11.5 documentation and implementation.
* Update Item class to better reflect 11.5 documentation and implementation.
* Fixing up optional object property syntax in a couple places (',' should have been ';')
* Updating Shaep class to better reflect 11.5 documentation and implementation.
* Updating Raster class to better reflect 11.5 documentation and implementation.
* Updating PathItem class to better reflect 11.5 documentation and implementation. Removed methods from Path that were inherited from PathItem.
* Updating Path class to better reflect 11.5 documentation and implementation.
* Updating CompoundPath class to better reflect 11.5 documentation and implementation.
* Updating Segment class to better reflect 11.5 documentation and implementation.
* Updating Curve class to better reflect 11.5 documentation and implementation.
* Updating CurveLocation class to better reflect 11.5 documentation and implementation.
* Updating Project class to better reflect 11.5 documentation and implementation.
* Updating Symbol to better reflect 11.5 documentation and implementation.
* Updating Style class to better reflect 11.5 documentation and implementation.
* Updating GradientStop class to better reflect 11.5 documentation.
* Updating Color class to better reflect 11.5 documentation and implementation.
* Updating View class to better reflect 11.5 documentation and implementation.
* Updating the event classes to better reflect 11.5 documentation and implementation.
* Updating TextItem to better reflect 11.5 documentation and implementation.
* More accurate return type guidance for event handlers. Small fix to resolve lint error (object[] changed to any[]).
* Added name to 'Definitions by' section in header.
* Adding an IHitTestOptions interface to improve the intellisense on a 14-property object capable of being paritally defined. Now users can create an object which includes any number of the 14 properties and get some guidance on what each property does. It's syntactic sugar and I'll allow that it may just be unecessary.
* More hittest tests
* Adding project to the hittest tests
* After some testing I like the IHitTestOptions approach much better. It provides CTRL+SPACE intellisense with descriptions. It also allows any previous code that sent an object with at least 1 property to pass the test. As such I've removed the object literal as it increases future maintainence.
* Updating hittests to make sure the right returns are coming from the hittest functions
* test documentation
* Adding the Example 'Boolean Operations' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Candy Crash' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* From reviewing the example Sadie Likes To Draw and looking through the implementation... it looks like the property "fully selected" is actually available on the parent Item and not first available on Path as indicated in the documentation.
* Adding the Example 'SatieLikedToDraw' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Chain' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Tadpoles' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Nyan Rainbow' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Fixing a namespacing issue resolving the Rectangle class in the Path.Rectangle and Path.Ellipse constructors
* Adding the Example 'Rounded Rectangles' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* The gradient components of a Color are sometimes undefined. Also origin and destination were missing from the documentation and definition. They are accessible for gradient colors.
* Adding the Example 'Radial Rainbows' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Item's appendTop and appendBottom methods were hiding in the documentation. They aren't listed in the main Item class, they're listed as inherited by all its children.
* Adding the Example 'Meta Balls' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Voronoi' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Future Splash' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Smoothing' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Spiral Raster' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Division Raster' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding equals and clone methods to Segment class.
* Adding the Example 'Q-bertify' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Path Intersections' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Path Simplification' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Example 'Hit Testing' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Adding the Gradient constructor that is missing from the documentation.
* Adding the Example 'Bouncing Balls' rewritten as typescript to the tests. This hopefully mimics what a user might have done to adapt the examples and ensure that all the example interfaces are implemented correctly.
* Reading through the code and examples shows that there are a few more options for constructing the GradientStop class than documented officially.
* Accidentally inserted a redundant declaration
* More options for the Gradient class constructor.
* Adding type-specific clones to all children of Item. This allows for user code to better reflect the clone operation without having to cast things all the time.
* new constructor, addition, and insertiong parameter options for Paths in order to enable more streamlined code which better matches examples from the code reference. Namely the ability to shorthand a point/segment as [x,y] arrays. Fixing a weird type warning by adding yet another on/off event overload.
* Added all of the example code found as paperscript inside the API documentation. Piece of code had to be rewritten to conform to typing strictness and I did my best to match the feel and brevity of the code. As possible I translated these shorthand notations into further improvements into the type definition. This included things like Point/Segment array shorthand for Path creation. To some degree I just applied my opinion on what users might prefer while still being guided by a type system. There are probably further tweaks we can make in this vein but I found the changes sufficient to make the example code require little porting effort.
* I just realized that I have two github accounts. Before I have too many commits to my name I wanted to merge accounts and as a result I need to update my profile link in the 'Definitions by' header.
