Hi @contributors Gladys
A quick message to let you know I did a bit of spring cleaning on the Gladys frontend ESLint configuration.
In the end, we’ve already been working on v4 for more than 2 years (time flies!), and this config hadn’t changed much:
Meanwhile, Preact released an official ESLint config that’s really good: GitHub - preactjs/eslint-config-preact: Unopinionated baseline ESLint config for Preact and Preact CLI codebases.
The Synacor config we were using was no longer maintained and was missing a lot of things
The famous browserslist that gives ESLint the list of browsers we support wasn’t up to date at all, and prevented us from using some features that are actually available in all modern browsers
Preact and preact-cli were updated recently — no major new features, but their config evolved: they removed polyfills that became unnecessary, fixed quite a few small bugs, and also updated their browserslist to stop building for outdated browsers!
Anyway, these are small things but ones you need to do from time to time.
I updated the configuration in this PR:
master ← upgrade-eslint-configuration
ouvert 01:44PM - 14 May 22 UTC
### Pull Request check-list
To ensure your Pull Request can be accepted as fa… st as possible, make sure to review and check all of these items:
- [ ] If your changes affects code, did your write the tests?
- [ ] Are tests passing? (`npm test` on both front/server)
- [ ] Is the linter passing? (`npm run eslint` on both front/server)
- [ ] Did you run prettier? (`npm run prettier` on both front/server)
- [ ] If you are adding a new features/services, did you run integration comparator? (`npm run compare-translations` on front)
- [ ] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to [the community](https://community.gladysassistant.com/) for testing before merging.
- [ ] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
- [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? See [the GitHub repo](https://github.com/GladysAssistant/v4-website) and the [website](https://gladysassistant.com).
- [ ] Did you add fake requests data for the demo mode (`front/src/config/demo.js`) so that the demo website is working without a backend? (if needed) See [https://demo.gladysassistant.com](https://demo.gladysassistant.com).
NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
### Description of change
Please provide a description of the change here. It's always best with screenshots, so don't hesitate to add some!
Feel free to do a quick rebase of your PR to see if there are changes to make on your side
If you have questions, this thread is the place for them!
4 Likes
Little spring cleaning with more than 16,000 lines modified!!
I wouldn’t want to be at your place when you do the cleaning, it must be wild!
2 Likes
It’s just the package-lock.json that changed a lot, it’s a generated file The PR is relatively small!