Within this PR, we are proposing two main updates. Firstly, we have modified the eslint-config-typescript-react and eslint-config-typescript-react-native packages to inherit from the @untile/eslint-config-typescript package. This change is implemented to enhance the consistency of rules across our Typescript and React-based projects, reducing code duplication and simplifying maintenance.
Secondly, we've made a decision to eliminate the tests residing within the eslint-config-typescript-react package. This action was taken because these tests were found to be duplicates of those present within both the eslint-typescript and eslint-react packages. We believe that this change will reduce redundancy and streamline our testing process.
These proposed changes contribute towards making our codebase more manageable, efficient, and consistent.
Within this PR, we are proposing two main updates. Firstly, we have modified the eslint-config-typescript-react and eslint-config-typescript-react-native packages to inherit from the @untile/eslint-config-typescript package. This change is implemented to enhance the consistency of rules across our Typescript and React-based projects, reducing code duplication and simplifying maintenance.
Secondly, we've made a decision to eliminate the tests residing within the eslint-config-typescript-react package. This action was taken because these tests were found to be duplicates of those present within both the eslint-typescript and eslint-react packages. We believe that this change will reduce redundancy and streamline our testing process.
These proposed changes contribute towards making our codebase more manageable, efficient, and consistent.