* Add missing FormState element to redux-form
According to the [example](https://redux-form.com/8.2.2/examples/submitvalidation/) on the redux-form page, it is possible to have a general error field for the whole form. I confirmed this behaviour with redux-form 8.2.6.
* Correct error formState type in redux-form
* Update react-dnd-touch-backend dnd-core dependency
dnd-core dependency goes from 4.5 to 9.3.1.
9.3.1 is the first version that fixes an incorrect export that is now
detected by Typescript 3.7.
I'm not sure this is the best fix, but I don't see a way to create a new
release of dnd-core@4.x either.
* remove react-dnd-touch-backend
* Fix incorrect import/export clashes.
A new error in Typescript 3.7 forbids name clashes like this:
```ts
import { X } from 'y'
export interface X { }
```
Previously they were incorrectly allowed. Typescript 3.7 will have a
beta version in the next day or two. In the meantime you can try
typescript@next -- the nightly build -- to see these errors.
* Missed a file!
* Update react-dependent tests for TS 3.7
Typescript 3.7 includes a flag that will allow people to migrate to the
currently-specified Class Fields ECMA proposal, which is currently at
Stage 3. When `--useDefineForClassFields` is turned on, Typescript
issues 3 new errors in places where the current Typescript semantics
would cause errors with the Stage 3 spec.
Two of the errors are very rare. The third is unfortunately common in
React code because its types don't allow the type of `context` to be
inferred. Instead, components redeclare `context` with an explicit type:
```ts
class ColumnSizerExample extends React.Component<any, any> {
context: React.ContextType<typeof MyContext>
}
```
Without `--useDefineForClassFields`, this *only* redeclares the type of
`context`. With `--useDefineForClassFields`, it redeclares the type of
`context` **and** initialises it to `undefined`. This is very
surprising.
To avoid this, Typescript 3.7 introduces new syntax for exactly this
scenario:
```ts
class ColumnSizerExample extends React.Component<any, any> {
declare context: React.ContextType<typeof MyContext>
}
```
However, Definitely Typed tests cannot use this new syntax because it
only works with Typescript 3.7, which isn't even in beta until next
week. So this PR uses two other workarounds instead:
1. Deleting the declaration when it has the same type as the base,
usually `any`. In this case it's redundant.
2. Using a dummy initialiser:
```ts
class ColumnSizerExample extends React.Component<any, any> {
context = {} as React.ContextType<typeof MyContext>
}
```
This is unfortunate, since it serves as a bad example to anyone reading
the tests. But I couldn't find any other way that works in all
Typescript configurations. I did, however, update the JSDoc for
`Component.context` with instructions to use the new syntax in TS 3.7
and above.
* Disable selected lint rules
* Add missing semicolon
Typescript 3.7 includes a flag that will allow people to migrate to the
Class Fields ECMA proposal as currently specified, which is at Stage 3.
When `--useDefineForClassFields` is turned on, Typescript
issues 3 new errors in places where the current Typescript semantics
would cause errors with the Stage 3 spec.
Two of the errors are very rare. The third shows up whenever classes want
to redeclare the type of a property from a superclass, usually when the
base property's type is `any` or `unknown`.
```ts
class ColumnSizerExample extends React.Component<any, any> {
context: React.ContextType<typeof MyContext>
}
```
Without `--useDefineForClassFields`, this *only* redeclares the type of
`context`. With `--useDefineForClassFields`, it redeclares the type of
`context` **and** initialises it to `undefined`. This is very surprising.
To avoid this, Typescript 3.7 introduces new syntax for exactly this scenario:
```ts
class ColumnSizerExample extends React.Component<any, any> {
declare context: React.ContextType<typeof MyContext>
}
```
However, Definitely Typed tests cannot use this new syntax because it
only works with Typescript 3.7, which isn't even in beta until next
week. So this PR uses several other workarounds instead:
1. Moving a constructor initialiser to a property declaration initialiser.
2. Using a dummy initialiser:
3. Adding type annotations so the type of the base property can be correctly inferred.
4. Deleting the declaration when it has the same type as the base. In this case it's redundant.
* add required property children to Props
* name function arguments for onCopy
* put required props before optional
* make all Options attributes optional and add format
* extend and add tests
* indicate lib version for these types and add contributor
* [react-calendar-timeline] Updated types to version 0.24.6
- Added absent types
- More test cases
- removed old non existent now props
* - few changes after review
* - few changes after review
* - test fix
* - fixes to header
* - fixes to labelFormat typings
* - fixes to labelFormat typings
* - fixes to typings
* returned object from defaults cannot be null/undefiend
* Update object.d.ts
* Update object.d.ts
* not required on any
* Update object.d.ts
* regenerate fp version
* add type definitions for channelgroup methods to pubnub type definitions
* fix the code formatting after husky configs butchered it
* add tests
* check in auto-formatted code
* Added type definitions for use-combined-reducers
* fixed errors
* fixed typo
* deleted typescript version declaration
* defined the same typescript version as react
* Started adding types.
* Missed these changes.
* Adding types.
* Should be good.
* Should be good to go.
* Updated prettier formatting.
* Updated prettier formatting.
* Updated prettier.
* Changed to ReadonlyArray.
* Modified as per review.
* Modified with other recommended changes.
* fix for error enum declaration
- moved error enum declaration outside of Parse context
- changed `const enum` to `declare enum`
- added static vars for enum fields to Error class
* added test for errors
* added xml-c14n typing
* reworked tests; added test run to package.json
* formatting fix
* removed package.json
* added info
* fixed errors
* rewrote typing
* reworked version
* added compile flag
* corrected export
* corrected export
* corrected tsconfig
* set noImplicitAny to false
* set other options to false
* returned back options which were turned off by mistake
* fixed typing according to review comment
* 17.2.0.34 added
* Added non-npm package
* Removed space
* added new line
added ew line
* Changed the word
* 17.2.0.46 added
* Removed blank line and added non-npm entry
* changed Encoding format
* 17.3.0.9-beta added
* added npm packages
added npm packages
* added npm packages
* format changes
* format changed
format changed
* Format changed to ANSI
* Update mongoose-paginate & mongoose-paginate-v2 populate types
* Add QueryPopulateOptions
* Upgrade typescript to 2.8 as the tslint does not succeed with the 2.3
