We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 7.14.0
Using intermediate destructuring of props in a class render method throws an exception. This seems to have been introduced in the v7.14.0 release
The following fails with VariableDeclarator ASTNodes are not handled by markPropTypesAsUsed:
VariableDeclarator ASTNodes are not handled by markPropTypesAsUsed
render() { const { chartData, chartTitle, loading, className } = this.props; const { legendData, title, tooltip } = chartTitle; ...
Whereas the following passes:
render() { const { chartData, chartTitle: { legendData, title, tooltip }, loading, className } = this.props; ...
Relevant propTypes are:
chartData: PropTypes.array.isRequired, chartTitle: PropTypes.object.isRequired, loading: PropTypes.bool.isRequired, className: PropTypes.string
I didn't expect the intermediate destructuring to fail, but if it is invalid then it should fail cleanly rather than throw.
The text was updated successfully, but these errors were encountered:
Duplicate of #2319. Fix is merged in master but waiting for release.
Sorry, something went wrong.
Just released v7.14.1 with the fix 🙂
v7.14.1
Great! thanks.
No branches or pull requests
Version 7.14.0
Using intermediate destructuring of props in a class render method throws an exception. This seems to have been introduced in the v7.14.0 release
The following fails with
VariableDeclarator ASTNodes are not handled by markPropTypesAsUsed
:Whereas the following passes:
Relevant propTypes are:
I didn't expect the intermediate destructuring to fail, but if it is invalid then it should fail cleanly rather than throw.
The text was updated successfully, but these errors were encountered: