[#1778] improvement(dashboard): Dashboard adds the ability to automatically format code.

[yl09099]

What changes were proposed in this pull request?

Introducing the front-end eslint code validation tool and formatting the front-end code.

Why are the changes needed?

Fix: #1778

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Existential test.

[github-actions]

Test Results

 2 434 files  ±0   2 434 suites  ±0   5h 0m 31s ⏱️ -23s
   937 tests ±0     936 ✅ ±0   1 💤 ±0  0 ❌ ±0 
10 857 runs  ±0  10 843 ✅ ±0  14 💤 ±0  0 ❌ ±0 

Results for commit 8793a31. ± Comparison against base commit 3d0c91a.

♻️ This comment has been updated with latest results.

[xianjingfeng]

Single quotes may be more suitable for front-end developers? @yl09099

[yl09099]

Single quotes may be more suitable for front-end developers? @yl09099

done. Format the code using the command "npx prettier . --write".

[xianjingfeng]

Single quotes may be more suitable for front-end developers? @yl09099

done. Format the code using the command "npx prettier . --write".

Could you add a job for checking style in the workflow?

[yl09099]

Single quotes may be more suitable for front-end developers? @yl09099

done. Format the code using the command "npx prettier . --write".

Could you add a job for checking style in the workflow?

Single quotes may be more suitable for front-end developers? @yl09099

done. Format the code using the command "npx prettier . --write".

Could you add a job for checking style in the workflow?

This format check rule is automatically triggered at compile time.

[xianjingfeng]

LGTM

[zuston]

Single quotes may be more suitable for front-end developers? @yl09099

done. Format the code using the command "npx prettier . --write".

Could you add this format command into the dashboard doc? @yl09099