Skip to content

fix: Remove react rule non-specific to security

Lucas Charles requested to merge drop-non-secure-eslint-react-rules into master

What does this MR do?

Remove react rule non-specific to security

react/no-unsafe - unsafe does not refer to the security but that the code is likely to have bugs in future versions

See https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Merge request reports