标准化类的加入

[TimChen44]

1. 提高效率不能只有后端的效率，与前端对接的效率也要提高，所以标准化了一些基础类
2. 提高效率最可怕的不是有多少工具，而是基于标准化后提供更高层面的整合，所以后续的能力会基于这些标准化开展

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/incidents/secrets) | NuGet API Key | 6cfef47cf25a163381b553d5cce864df82245632 | .github/workflows/nuget_publisher.yml | [View secret](https://github.com/786744873/easytool/commit/6cfef47cf25a163381b553d5cce864df82245632#diff-96ee448c242f60b7476f2f119053b6a4R38) | | [-](https://dashboard.gitguardian.com/incidents/secrets) | NuGet API Key | 0e7f3187dd0e46cdc862522636331451da6e4a2f | .github/workflows/nuget_publisher.yml | [View secret](https://github.com/786744873/easytool/commit/0e7f3187dd0e46cdc862522636331451da6e4a2f#diff-96ee448c242f60b7476f2f119053b6a4L38) | | [-](https://dashboard.gitguardian.com/incidents/secrets) | NuGet API Key | 0e7f3187dd0e46cdc862522636331451da6e4a2f | .github/workflows/nuget_publisher.yml | [View secret](https://github.com/786744873/easytool/commit/0e7f3187dd0e46cdc862522636331451da6e4a2f#diff-96ee448c242f60b7476f2f119053b6a4R38) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/detectors/specifics/nuget_api_key#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>