-
As of now, there's no good way to use the client library without frequently referring to the API docs. Type definitions (in the form of a `*.d.ts` file) would make the library much more accessible. Pl…
-
Went looking to use `found-relay` with a TypeScript/React project and was unable to do so as all of the examples depend on `farce` and its history management, which does not have TypeScript type defin…
-
Consider the following schema:
https://unpkg.com/@octokit/webhooks-schemas@7.3.1/schema.json
it contains a definition:
```json
"pull_request$closed": {
"$schema": "http://json-sch…
-
### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
E.g. ONNXRuntime has a C API that puts all entry points as function pointers into an OrtApi struct…
-
Reference comment: https://github.com/cosmos/ibc-go/pull/6103#discussion_r1559121898
We should try and not mix and mash pointer-value receivers on methods and instead consistently use one or th…
-
Hi again! As the tool can now be run programmatically, it would be good if there were also type definitions available for those of us trying to run this in a TS codebase.
The options are:
1. Add t…
-
The type definitions in this library seem to not include the response type.
E.g. here is the `index` type definitions.
```ts
index<
TResponse = Record,
TRequestBody extends RequestBod…
-
How would you feel about adding Typescript type definitions to these packages?
-
They would be useful for those of us using TS.
Here's the current definition I'm using:
```ts
declare module 'mention-hashtag' {
export enum ExtractionType {
MENTION = '@',
HASH_TAG …
-
It would be useful to have the option to group definitions by type, which would later be sorted. In other words interfaces together, enums together etc.
qrsor updated
4 years ago