* [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
* Creating new package for "storybook_addon-readme"
This is my first time writing a type definition file. There should be something wrong. Please take a look and help me making this better...
* fix name & lint
1. dt-header
--> from "4.0.0-beta1" to 4.0
2. no-declare-current-package
--> move to the subfolder. Not sure If It works.
3. strict-export-declare-modifiers
--> add "export" to all the type/interface
4. Could not parse version: line is '// TypeScript Version: 3.0.3'
--> Lower to 2.9
* fix npm test
1. Unnecessary "./" at the start of ~~
--> remove "./" part from tsconfig.json
* fix npm test error
1. Error: Expected file 'src/storybook-readme-tests.tsx' to be named storybook-readme-tests.ts
--> change accordingly
* fix npm test eror
1. change name
* fix npm test error
1. change name
* wht src...
* hm...
* path..?
* versino?
* versin
* what..
* versino
* path mapping...
* marked
* move..
* 역시 상위로 가야하나.
* fix npm test
1. Unnecessary "./" at the start of ./src/withReadme.d.ts
--> remove it all
* fix npm test
1. problem with test file at the subfolder
--> Move to the root level
2. parseDependencyVersionFromPath error
--> remove paths from tsconfig.json
* add "components/Marked.d.ts"
* fix
1. correct Project url
2. correct Marked to export default (I somehow changed to export during the commits...)
* hm... correct typo
* 1. Write tests with storiesOf from @storybook/react
2. Add "paths" to tsconfig for fixing importing problem of @storybook/readme
3. Fix Errors that has appeared after real test using storiesOf
* Moved all the types to index.d.ts as "andy-ms" suggested
* Remove src/* from tsconfig files as moving all the types to index.d.ts
* Fix "npm lint storybook-readme"
1. I'm just curious why all the types should be exported.
Isn't it cleaner putting "export" to only actually used types? (such as withDocs, wthReadme, Doc, Marked)
Hm.. or maybe... to be used from actual user?
* Merge upstream Pull from DefinitelyTyped
* fix for andy-ms review
1. Change to overloading with namspace style
2. Avoid intersection type and change to function overloading
3. Change Typescript Version to Minimum version that works
* I tested from 2.3 to upward because of failing npm test with "storybook-readme depends on react but has a lower required TypeScript version."
version 2.8 is the lowest version I could go with. Is It my local setting that made this problem? I'm not sure...
* add types for pkcs7
* bump version number
* revert change of node-forge version number
* mark content/contentInfo as optional and add arg for sign(options?)
* Add typings for extension API
This commit adds types to most of the API that is used when writing a extensions for `markdown-it`. Plus there are some minor improvements.
* fix errors emitted by linter
* increase version of dependencies
* oops, I forgot one
* Add type for StateInline.delimiters
* [query-string] Make types more accurate
* Update index.d.ts
* Fix ts errors
* Fix linter errors
* Fix types and make tests more accurate
* Fix linter errors
* stylelint: add types for creating custom rules
Covers `stylelint.utils` and `stylelint.createPlugin'
* stylelint: use the proper LintResult definition
* [react-bootstrap] remove incorrect exports
several sub-components are exported in index.d.ts, when they are not
in the library itself.
should fail:
`import { DropdownMenu } from 'react-bootstrap';`
should succeed:
`import { Dropdown } from 'react-bootstrap';`
`import DropdownMenu from 'react-bootstrap/lib/DropdownMenu';`
* [react-bootstrap] fix Dropdown.Menu typing
DropdownMenu uses `export =`, so the import must use require, `import *`.
this matches the pattern in Carousel, FormControl, etc.
-1 and 1 aren't the only numbers allowed. Any number less than or greater than 0 will sort the item properly.
This enables shortcuts like (a, b) => a - b;
Restricting the signature to -1 | 0 | 1 is a mistake.
* offset, endOffset and repeat in the Pattern Interface can also be of type string
* added a few new tests with new string offset, endOffset and repeat
