CSS rule part 2 (stylelint)
Meeting Info ¶
| Date | 2022-09-15 |
|---|---|
| Topic | CSS rule part 2 (stylelint) |
| Attendee | Calvin Yan, Rocky Chi, Selly Huang, Daniel Zhou, Ted Zhao, Jackson Liu, Kevin Qian |
| Note Taker | Jackson Liu |
| Timer | Daniel Zhou |
| Duration | 60 minutes |
Meeting Agenda ¶
1. Sync Pylint report research status (if capable) - 10 mins
2. Sync Checkstyle report research status (if capable) - 10 mins
3. Discuss on CSS rules part2 - 20 mins
Meeting Minutes ¶
1. Sync Pylint report research status ¶
Kevin mentions only the Pylint of old version support HTML as output format. Currently, EMS has a markdown doc, they could format JSON to display at the markdown doc. EMS might code a new static page to display the report for internal use.
Team members think using Jenkins pipeline to output the reports is better. Use a Jenkins plugin to integrate Pylint check. Need more search to get to know this plugin, and there is no need to export these result to markdown format
2. Sync Checkstyle report research status ¶
Ted demonstrates a Plugin, [Warnings Next Generation](https://plugins.jenkins.io/warnings-ng/).
This plugin contains most lint checks, we could customize the checks we need. And the results can be visualized. It’s very clear and impressive.
3. Discuss on CSS rules part 2 ¶
Since there is not controversies among these options, Jackson mainly talks about each rules during this meeting.
4. Reference ¶
Action Items ¶
Research this plugin (Warnings Next Generation) for Stylelint, Pylint, and Eslint.