Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
typescript:
microsoft/TypeScript#38535
I got the same error, I have fixed it
XY is specified more than once, so this usage will be overwritten.
This spread always overwrites this property.
It is valid: table has the rowHeight and headerHeight prop twice, cause in tableProps these are mandatory.
New tslib version is not compatible with react-quill we should check it after this released: zenoamaro/react-quill#549 (now it has only beta version)
webpack:
the plugin now accepts an object, you should change new CopyPlugin(patterns, options) to new CopyPlugin({ patterns, options })
Eslint breaking changes:
@typescript-eslint/explicit-module-boundary-types: Missing return type on function. --> now it throw warning ( I have disabled it till we fix these problems)
@typescript-eslint/prefer-as-const: Expected a
const
instead of a literal type assertion ( I have disabled it till we fix these problems)@typescript-eslint/ban-ts-comment: Don't use
object
as a type. Theobject
type is currently hard to use etc. ( I have disabled it till we fix these problems)@typescript-eslint/no-extra-non-null-assertion ( I have disabled it till we fix these problems)
@typescript-eslint/no-extra-semi ( I have disabled it till we fix these problems)
@typescript-eslint/no-non-null-asserted-optional-chain" ( I have disabled it till we fix these problems)
@typescript-eslint/ban-types ( I have disabled it till we fix these problems)
"@typescript-eslint/camelcase": "error", is removed so I delete these comments from code: // eslint-disable-next-line @typescript-eslint/camelcase
New version of Monaco-editor is still not working with our code
Action plan:
recommended
sets for 3.0.0 typescript-eslint/typescript-eslint#1423)