style: format code with Prettier and StandardJS

[deepsource-autofix]

This commit fixes the style issues introduced in b0f9b21 according to the output
from Prettier and StandardJS.

Details: None

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pro-react-admin	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 25, 2024 2:46am

[what-the-diff]

PR总结

• 更改了HTML元素的表达方式
  我们将<section className={styles.line}></section>变为了自闭合标签<section className={styles.line} />，简洁明了。
• 更新了组件属性的表达方式
  将触发属性triggerOnce={true}简化为triggerOnce，更为简洁和可读。
• 统一了HTML元素表达格式
  优化了SpotlightCard中的<section></section>，采用自闭合标签: <section />，使代码更加整洁。
• 改变了样式类名的引用方式
  我们把<button className={styles['button']} ...>更改为了点记号引用类名<button className={styles.button} ...>，使代码更清晰易读。
• 转换了多个HTML元素为自闭合标签
  将多个<div className={styles['circle-x']}></div>元素转变为自闭合标签<div className={styles['circle-x']} />，使代码更整洁简洁。

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Qodana for JS

371 new problems were found

Inspection name	Severity	Problems
ESLint	🔴 Failure	227
Unused import	🔶 Warning	13
Unused local symbol	🔶 Warning	10
Unnecessary non-capturing group	🔶 Warning	6
Mismatched JSDoc and function signature	🔶 Warning	4
Redundant local variable	🔶 Warning	4
Redundant character escape	🔶 Warning	3
Import can be shortened	🔶 Warning	2
Equality operator may cause type coercion	🔶 Warning	1
Unused assignment	🔶 Warning	1
Void function return value used	🔶 Warning	1
Duplicate character in character class	🔶 Warning	1
Unresolved JSX component	◽️ Notice	73
Deprecated symbol used	◽️ Notice	12
Result of method call returning a promise is ignored	◽️ Notice	8
Duplicated code fragment	◽️ Notice	2
Regular expression can be simplified	◽️ Notice	2
Missing await for an async function call	◽️ Notice	1

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions