* @types/remarkable had some holes when it came to writing plugins. See the CHANGELOG.md for information
* @types/remarkable had some holes when it came to writing plugins. See the CHANGELOG.md for information
* refactor values to support derferred executions
* remove unneeded dependency
* fix catastrophic, world-ending newline that crept in
* fix tslint problems
The `swiper` module provides only a default export of the Swiper class,
while the `swiper/dist/js/swiper.esm` provides named exports of this
class as well as the Swiper "modules".
Also comply with no-declare-current-package dtslint rule.
See https://stackoverflow.com/q/52673117 .
* added types for yup@0.26
* added types for is-docker
* Revert "added types for is-docker"
This reverts commit 753dac6d555112d294caf27c931b1e8cbb79045c.
* Modify subscription types to use the correct callbacks and subscription handle structures
* The listeners are actually the same subscription handles under the hood
* Not sure what this scope variable would look like, not seeing any clues in cometd. Going with any.
* Make exec / createRow methods generic
Saying they take/return Object is inaccurate, I wasn't sure if they should use object, any, or T extends object. I went with T extends object since it seems most correct.
* Update tests
* Update lint
* Replace generic with object from "Common Mistakes"
* Make History object generic
* Make History object generic
* Fix MemoryHistory definition, Fixed tested
* [jquery] Fix code for example not rendering in VS Code autocomplete.
VS Code does not render the code block of the last example in the autocomplete tooltip (but does in the hover tooltip). This is fixed by adding an additional line terminated by a zero-width space. There doesn't appear to be an obvious pattern to what causes this and there may be other incidences of this bug in the declarations.
* [jquery] Improve formatting of documentation for unified signatures in tooltips.
Documentation for unified signatures is also unified. This means that documentation for a parameter will contain documentation from all the parameters that it's composed of. VS Code and WebStorm render this as one continuous line. This makes it confusing as it's not obvious which parts of documentation apply to a parameter.
To remedy this, parameters are formatted as a bulletted list. `<br>` tags are necessary to force line breaks in WebStorm. The list also cannot start on the first line. To force the first line break, the `<br>` tag is used for WebStorm. For VS Code, a non-empty body must follow the parameter name on its line. A Braille Pattern Blank could be used here but to provide a more intuitive and consistent experience, VS Code's format for rendering parameter info is mimicked instead. The `@` symbol must be encoded to prevent `@param` from being parsed as a JSDoc tag.
Note: VS Code renders the `<br>` tags literally and there does not appear to be a way to hide them.
* Quill Options Fix to Match Documentation
https://quilljs.com/docs/api/#debug
Debug can take a string or boolean.
* Version Up
* CI Failed
* Adding test
* [stellar-sdk]: Fix AccountRecord.data and data_attr
data is a function to call the /accounts/{id}/data/{key} endpoint, while data_attr is an object bag containing data for the account.
* [stellar-sdk] Add overload to toXDR() which accepts a string encoding
* react-onsenui: Added missing attributes to existing components and on-change event of a Switch.
* react-onsenui: Fixed typo for ProgressBar intermediate --> indeterminate
* react-onsenui: Fixed type for ProgressBar secondaryValue boolean --> number
* react-onsenui: Fixed type definitions for Carousel and CarouselItem: modifier is optional and itemWidth/itemHeight may be string as well.
* react-onsenui: increased version number
Andy