* Update stale documentation for axis titles (#9682)
Updated the documentation for the types on axis labels.
In the corresponding `index.esm.d.ts` file, put JSDoc descriptions for
the properties to match the now-updated documentation.
* Clean up axis title labels documentation (#9682)
Inserted extra information in the documentation for the type of the
padding, inserted missing full stops.
In the type file, added JSDoc for undocumented properties.
* Update docs/axes/labelling.md
* Update types/index.esm.d.ts
Co-authored-by: Jukka Kurkela <jukka.kurkela@gmail.com>
* Define with let to avoid "assignment to constant" errors
Thanks for this example. Defining `label` with `const` rather than `let` results in `Uncaught TypeError: Assignment to constant variable.`
* Another case where const needs to be replaced with let.
* Requested cases where const needs to be replaced with let +1 (style).
* Fix cleaning up metasets
I believe it's a mistake to only delete the metaset if it has a valid controller; see f191f2f5 for where this behavior was introduced.
This is a minimal fix for #9653; as discussed there, it may also be worth updating `updateHoverStyle`.
As of #7030, `this._metasets` should always be defined, so checking whether it's undefined is no longer necessary.
* Add a test covering metaset behavior
* Add a regression test for #9653; fix `toHaveSize` usage
* Fix test failure
* Update linear.md
* Update padding.md
* Update padding.md
* Update padding.md
* Update padding.md
* Update padding.md
* Update padding.md
* Update padding.md
* Update padding.md
* Update padding.md
* Padding.md links work now
* Decimation plugin links work now
* Three links work now
I’ve made the Specify a rotation value and ticks.sampleSize links work.
* Update linear.md
This makes it easier to use the `karma` CLI directly, if desired, and makes it easier to use WebStorm's integrated debugger (which makes up `karma` command-line invocations itself). Prior to this change, if `--grep` isn't given, Karma looks for `*undefined*.js` and finds no tests to run.
Otherwise, repeated lookups of undefined properties always trigger the
comparatively expensive resolution. This can be the case for example in
_calculateBarIndexPixels() in controller.bar.js when looking up
options.skipNull and options.maxBarThickness, which is done for each bar
in a bar chart.
