* Allow `null` maps for `MeshBasicMaterial`s
A mesh can optionally have a `map` but right now this doesn't allow us to remove a material's map by setting it to `null`, which is the default value for maps.
* All textures are nullable
https://threejs.org/docs/#api/en/materials/MeshStandardMaterial
* Lots of other things are nullable, too
* Fix indentation
My editor changed the indentation of this file.. oops.
* Actually fix indentation
* Added no-argument overload for Model.previous
`Model.previous()` in Sequelize called with no arguments returns an object containing the previous keys and values for properties that have changed. This pull request adds this overload to the Model.d.ts type definition file along with a comment documenting it.
* Added test for Model.previous w no arg
* add types for browserify/commonjs-assert
* fix tests and rename to 'assert'
* fix some linting errors, checking in to avoid closing of pull request
* fixed all lint errors
* [jquery] `isNumeric` can not be a user defined type guard.
`isNumeric` can return true for strings in addition to numbers, but only for a subset of either. It'll return false for NaN (which TypeScript treats as a number) and for strings which cannot be parsed as a number.
* [jquery] `isPlainObject` can not be a user defined type guard.
Due to the imprecise way with how `PlainObject` is declared, `isPlainObject` can not be a user defined type guard.
* [jquery] Use https for links.
* [jquery] Fix link for `JQuery.jquery`.
* [jquery] Remove empty line before `@deprecated`.
For consistent formatting since examples were added.
* [jquery] Document additional `extend` parameters.
* [jquery] Improve declarations of `data()` to catch unintentionally passing `undefined` as a value.
This handles the more likely case of users passing a value that is possibly undefined.
* [jquery] Improve declaration of `css()`.
* [jquery] Minor improves to `proxy()` documentation.
* [jquery] Fix region folding for WebStorm.
WebStorm uses `// #region` to designate a region start while VS Code uses `// region`. They can both (must, in this case) be terminated using `// #endregion`. Using both `// #endregion` and `// endregion` results in odd behavior in both editors.
* ramda: add return type assertions for filter/reject test
* ramda: Add failing test for filter-in-pipe scenario
* ramda: Workaround for type inference problem in Filter
In the `Filter` type, when used inside a pipe, the second format always took
precedence in type inference, causing problems when a list was filtered.
With this change, you can manually specify whether you are using filter
for an array or an object, so usage in a pipe will work. You can also
leave out the second type parameter, in which case filter works as
previously.
```ts
import { pipe, filter } from 'ramda';
pipe(
filter<string, 'array'>((val: string) => val.length > 2),
)(['list', 'or', 'object']);
pipe(
filter<string, 'object'>((val) => val.length > 2),
)({ a: 'list', b: 'or', c: 'object' });
```
Jackson Delahunt