feat: add jsx-no-useless-fragment (#69)

* BREAKING CHANGE: add jsx-no-useless-fragment

* doc: precise what to do when you add a rule

* feat: add a pull request template

Author: clementDours

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,3 @@
+<!-- If your PR is related to a RFC, please add `Closes #<issue number>` to link the PR to the issue and close it automatically when the PR is merged -->
+
+<!-- We use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) to automate the release process. Please follow the commit message format described in the link above. Lerna will automatically generate the changelog for each package based on the commit messages since the last version. -->

README.md

@@ -55,6 +55,8 @@ Changes:
 
 It will then push a tagged commit `chore(release): Publish` which will then trigger the Github Workflow to publish the new version of each package to NPM.
 
+> If you add a new rule to a config, this is a breaking change, because it could make the CI fail on projects that use the plugin. The commit name where you add the new rule needs to follow this patern `BREAKING CHANGE : the description of your commit`
+
 ## Running commands
 
 - `yarn lerna run start`: run the 'start' script in all packages (currently only present in `example-app`),

packages/eslint-plugin/lib/configs/recommended.js

@@ -40,6 +40,7 @@ module.exports = defineConfig({
     "react/no-unstable-nested-components": "error",
     "react/prop-types": "off",
     "react/no-unused-prop-types": "error",
+    "react/jsx-no-useless-fragment": "error",
     "@typescript-eslint/no-unused-vars": "off",
     "unused-imports/no-unused-imports": "error",
     "unused-imports/no-unused-vars": "error",