Pylint & ESlint report research status and CSS rules Meeting Minutes

Meeting Info ¶

Meeting Agenda ¶

1. Sync Pylint report research status (if capable) - 5 mins
2. Sync ESLint report research status (if capable) - 5 mins
3. Discuss on CSS rules - 30 mins

Meeting Minutes ¶

Sync Pylint and ESLint report research status ¶

• Kevin didn't have time to research Pylint report, so he will continue focusing on this task.
• Jackson shared below commands to export ESLint scanning HTML report which can be tables.

  eslint -f stylish --config.eslintrc.js --ext .vue,.ts,.js src > results.txt
  eslint -f table --config.eslintrc.js --ext .vue,.ts,.js src > results.txt
  eslint -f html --config.eslintrc.js --ext .vue,.ts,.js src > results.txt
  

• Rocky shared some ideas as below: 1. We should generate the HTML lint report in Jenkins build console. 2. We can apply lint scanning in change pipeline as one node. 3. If the lint scanning node has any errors, we should stop going code building node. 4. We just need to show error details on lint scanning node if having any scanning error.

Discuss on CSS rules ¶

• CSS rules survey result (marked):

• We should add one more rules according to this wiki

Action Items ¶

1. Research how to generate the lint scanning HTML report by Jenkins plugin - Jackson.
2. Research how to apply lint scanning into change pipeline - Jackson.
3. Add one more CSS rules expect for this meeting's CSS rules survey - Jackson.
4. Go on researching Pylint report generation - Kevin.
5. We must @ next daily tip host after own daily tip share is done.