Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Angular & Express dependencies to their latest versions #17

Merged
merged 21 commits into from
Sep 14, 2024
Merged

Conversation

vnobo
Copy link
Owner

@vnobo vnobo commented Sep 14, 2024

✨ feat(boot/platform/src/main/java/com/plate/boot/commons/utils/query/QueryJsonHelper.java): 增强查询JSON助手类,优化排序与条件构造逻辑优化了QueryJsonHelper类,以便更高效地ON序列化,改进SQL条件子句生成以支持查询嵌套的JSON属性,并精细处理特殊操作如'Between', 'In'等在SQL环境中的应用。此外,重构了方法以增强代码可读性和维护性。
📦️ chore(package): Update Angular & Express dependencies to their latest versions
📦️ chore(package-lock.json): Update Angular dependencies to version 18.2.4
⬆️ chore(package.json): Update Angular dependencies to version 18.2.4
✨ feat(boot/platform/src/main/java/com/plate/boot/commons/utils/query/QueryJsonHelper.java): Enhance query condition and sorting handling, enabling camelCase conversion for JSON fields to improve SQL query adaptability.
🔧 refactor(QueryJsonHelper.java): 优化 SQL 查询构造逻辑,支持嵌套 JSON 属性查询。 📝 docs(settings.json): 更新 VSCode 配置,添加 Codegeex 提交信息风格设置。
✨ feat: 优化查询和转换逻辑,添加 JsonPointerException 异常处理,完善 UserAuditorConverters 注释,调整 LoggerRequest 构造方法,增强 AbstractDatabase 查询功能,改进 ContextUtils 和 BeanUtils 工具类
✨ feat(query-utils): 引入 QueryCondition 记录类型并优化动态 SQL 构建逻辑- 添加 QueryCondition 记录类型以清晰表达查询条件。

vnobo added 21 commits August 24, 2024 14:55
升级了包括Angular、ng-zorro-antd和devkit在内的关键依赖项,以确保库的性能和兼容性。这些更新涉及版本从18.2.0到18.2.2的Angular组件,以及从18.1.0到18.1.1的ng-zorro-antd版本更新。同时,调整了构建和CLI工具以匹配这些升级。
- 更新 ng-ui 代理配置指向新端口
- 优化 QueryJson 排序逻辑处理默认情况
- 优化 LoggersService 中的搜索与分页查询逻辑
- 添加 LoggerRequest 绑定参数 SQL 功能
- 更新 QueryJson 处理空参数情况及优化 JSON 路径构建
* ParamSql updated for clearer SQL parameter structure and documentation.
* CriteriaUtils extended with pagination, sorting utilities, and parameter building for dynamic SQL.
* Introduced JsonException to manage JSON processing issues with detailed status messages.
* Enhanced QueryJson for constructing JSON path-based queries and sorting.
* BeanUtils upgraded with JSON path bean conversion, cache key gen, and advanced copying features.
* RestServerException now supports custom error codes and detailed messaging.

These refinements optimize data manipulation, error management, and query dynamics.
…documentation"

This commit refines the converter classes by enhancing their documentation and structure for better clarity and future maintenance. It adds detailed JavaDoc comments explaining the purpose and usage of each converter class and method, ensuring that developers can understand their roles within the application easily. Additionally, it removes unnecessary comments and author tags, focusing on functional descriptions and improving the overall quality of the codebase.
…caching, and initialization

Refactor AbstractService and AbstractDatabase to include comprehensive documentation explaining their roles, integrated caching mechanisms, and improved initialization processes. Updates ensure clear understanding and optimized performance for service and database operations within the application. Additionally, refined commit hooks to enforce consistent commit message standards.
In this commit, the unnecessary todo comment within the BaseEntity class's setCode method has been removed
Update service classes and entities to use the new `QueryHelper` utility methods instead of the deprecated `CriteriaUtils`. This change streamlines query construction and ensures consistency in handling query parameters and pagination.

The commit includes modifications to multiple files, replacing instances of `CriteriaUtils` method calls with their `QueryHelper` equivalents and adjusting import statements accordingly. Additionally, it renames related classes like `ParamSql` to `QueryFragment` to reflect the updated utility usage.
- Introduce `QueryFragment` for concise query fragment construction.
- Rename `buildParamSql` to `query` for clarity on function.
- Refactor query building logic for improved readability and maintainability.

This commit enhances the query generation utilities, ensuring more adaptable condition handling and streamlined sorting configurations while refining the code structure for easier understanding and future development.
- 更新 `QueryJsonHelper` 中的键分隔符处理逻辑。
- 调整 `UserAuditorConverters` 文档注释及内部转换器逻辑。
- 优化 `QueryHelper` 的 SQL 构建过程。
- 添加 `JsonPointerException` 异常类处理 JSON 指针错误。
- 扩展 `LoggerRequest` 构造方法与日志细节。
- 修正 `AbstractDatabase` 中的转换器调用。
- 更新 `JsonException` 以处理更广泛的异常类型。
- 增强 `ContextUtils` 和 `BeanUtils` 方法功能。
- 添加 `QueryCondition` 记录类型以清晰表达查询条件。
- 在 `QueryJsonHelper` 中增强错误处理与 JSON 查询路径构建。
- 优化 `QueryHelper` 中的条件生成逻辑,支持特殊关键字处理与参数化构建。
- 调整 `LoggerRequest` 的 `buildQueryFragment` 方法以适配新逻辑。
…rs 注释,调整 LoggerRequest 构造方法,增强 AbstractDatabase 查询功能,改进 ContextUtils 和 BeanUtils 工具类
📝 docs(`settings.json`): 更新 VSCode 配置,添加 Codegeex 提交信息风格设置。
…y/QueryJsonHelper.java`): Enhance query condition and sorting handling, enabling camelCase conversion for JSON fields to improve SQL query adaptability.
…y/QueryJsonHelper.java`): 增强查询JSON助手类,优化排序与条件构造逻辑

优化了`QueryJsonHelper`类,以便更高效地处理JSON查询参数,包括转换排序规则为驼峰命名以适应JSON序列化,改进SQL条件子句生成以支持查询嵌套的JSON属性,并精细处理特殊操作如'Between', 'In'等在SQL环境中的应用。此外,重构了方法以增强代码可读性和维护性。
@vnobo vnobo self-assigned this Sep 14, 2024
Copy link

gitguardian bot commented Sep 14, 2024

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
8529663 Triggered Username Password a7a9499 boot/platform/src/main/resources/application-local.yml View secret
🛠 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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. 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


🦉 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.

@vnobo vnobo merged commit 1bacca9 into main Sep 14, 2024
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant