* refactor: remove useless code related 'TableField'
* refactor: add details block UI schema and hooks
* refactor: update details block schema and create new hook for details block without paging props
* refactor: add useDetailsBlockWithoutPagingDecoratorProps and useDetailsBlockWithPagingDecoratorProps
* test: add unit tests
* chore: fix build
* chore: fix import path for withDynamicSchemaProps
* fix: fix import typo in createDetailsBlockWithoutPagingUISchema test
* chore: fix unit test
* refactor: should not get collection on getting association in UISchema
* chore: fix unit test
* refactor: use x-use-component-props instead of useProps
* chore: fix Pagination
* chore: skip weird tests
* chore: remove weird test
* refactor: update details block initializers and associated schemas
* refactor: rename to useDetailsWithPaginationProps
* refactor: rename to useDetailsWithPaginationDecoratorProps
* refactor: rename to createDetailsWithPaginationUISchema
* chore: fix unit test
* refactor: rename to createDetailsUISchema
* refactor: rename to useDetailsDecoratorProps
* refactor: rename to useDetailsProps
* refactor: rename to 'blockSettings:details'
* chore: fix e2e
* refactor: migrate createGridCardBlockSchema to modules
* refactor: add grid-card block hooks and decorator props
* refactor: should not get collection on getting association in UISchema
* refactor: use x-use-component-props instead of useProps
* chore: fix build
* refactor: kanban
* refactor: gantt
* refactor: map
* refactor: calendar
* refactor: compat
* refactor: rename to createKanbanBlockUISchema
* refactor(kanban): use x-use-component-props instead of useProps
* refactor(Gantt): rename to createGanttBlockUISchema
* refactor: use x-use-component-props instead of useProps
* refactor: rename
* refactor(Map): use x-use-component-props instead of useProps
* refactor(Calendar): rename
* refactor(Calendar): should not get collection on getting association in UISchema
* refactor(Calendar): use x-use-component-props instead of useProps
* chore: add comment
* chore: fix unit test
* fix: add scopes to fix e2e
* fix(Calendar): add association property to CalendarBlockProvider decorator
* test: add e2e for Calenndar
* refactor: extract to common options
* refactor: migrate to modules
* test: add unit test
* refactor: use x-use-component-props instead of useProps
* chore: fix unit test
* chore: rename
* fix: useExpressionScope
---------
Co-authored-by: chenos <chenlinxh@gmail.com>
* refactor: refactor list block initializer and record association list block initializer
* refactor: add useListBlockDecoratorProps
* chore: fix import path to avoid build error
* refactor: should not get collection on getting association in UISchema
* refactor: use x-use-component-props instead of useProps
* chore: fix unit test
* refactor: extract to createCreateFormBBlockUISchema
* refactor: extract to createEditFormBlockUISchema
* refactor: use new function to create UISchema
* refactor: add x-use-decorator-props
* fix: add withDynamicSchemaProps to FormBlockProvider
* chore: update import path for withDynamicSchemaProps
* refactor: should not get collection on getting association in UISchema
* refactor: use x-use-component-props instead of useProps
* fix: fix withDynamicSchemaProps
* chore: fix unit test
<!-- Note -->
<!-- This is a template for submitting a new feature.
Use the bug fix template if you're submitting a bug fix pull request by adding `template=bug_fix.md` to your pull request URL. -->
# Description
<!-- Describe the new feature or modification to an existing feature clearly and consciously. -->
# Motivation
<!-- Explain the reason for adding or modifying this feature. -->
# Key changes
<!-- Provide a technically detailed description of the key changes made. -->
- Frontend
- Backend
# Test plan
## Suggestions
<!-- Provide any suggestions or recommendations for improvements in the testing plan. -->
## Underlying risk
<!-- Identify any potential risks or issues that may arise from the new feature or modification. -->
# Showcase
<!-- Including any screenshots of the new feature or modification. -->
Reviewed-on: daoyoucloud/tachycode#510
Reviewed-by: sealday <zhanglin@daoyoucloud.com>
Co-authored-by: bai.jingfeng <bai.jingfeng@foxmail.com>
Co-committed-by: bai.jingfeng <bai.jingfeng@foxmail.com>
* fix: e2e-failed
* fix: ci
* fix: ci bug
* fix: ci(skip server ci)
* fix: ci [skip ci]
* fix: ci(skip server ci)
* fix: ci
* fix: ci
* fix: remove skip if
---------
Co-authored-by: dream2023 <1098626505@qq.com>
<!-- Note -->
<!-- This is a template for submitting a new feature.
Use the bug fix template if you're submitting a bug fix pull request by adding `template=bug_fix.md` to your pull request URL. -->
# Description
<!-- Describe the new feature or modification to an existing feature clearly and consciously. -->
# Motivation
<!-- Explain the reason for adding or modifying this feature. -->
# Key changes
<!-- Provide a technically detailed description of the key changes made. -->
- Frontend
- Backend
# Test plan
## Suggestions
<!-- Provide any suggestions or recommendations for improvements in the testing plan. -->
## Underlying risk
<!-- Identify any potential risks or issues that may arise from the new feature or modification. -->
# Showcase
<!-- Including any screenshots of the new feature or modification. -->
Reviewed-on: daoyoucloud/tachycode#505
Co-authored-by: wjh <wwwjh0710@163.com>
Co-committed-by: wjh <wwwjh0710@163.com>
<!-- Note -->
<!-- This is a template for submitting a new feature.
Use the bug fix template if you're submitting a bug fix pull request by adding `template=bug_fix.md` to your pull request URL. -->
# Description
<!-- Describe the new feature or modification to an existing feature clearly and consciously. -->
# Motivation
<!-- Explain the reason for adding or modifying this feature. -->
# Key changes
<!-- Provide a technically detailed description of the key changes made. -->
- Frontend
- Backend
# Test plan
## Suggestions
<!-- Provide any suggestions or recommendations for improvements in the testing plan. -->
## Underlying risk
<!-- Identify any potential risks or issues that may arise from the new feature or modification. -->
# Showcase
<!-- Including any screenshots of the new feature or modification. -->
Reviewed-on: daoyoucloud/tachycode#504
Co-authored-by: bai.jingfeng <bai.jingfeng@foxmail.com>
Co-committed-by: bai.jingfeng <bai.jingfeng@foxmail.com>
* feat: input number support display format
* feat: input number support display format
* feat: input number support display format
* feat: input number support display format
* feat: input number support display format
* feat: input number support display format
* refactor: local improve
* refactor: local improve
* refactor: code improve
* refactor: locale improve
* test: input-number
* test: input-number
* test: input-number
<!-- Note -->
<!-- This is a template for submitting a new feature.
Use the bug fix template if you're submitting a bug fix pull request by adding `template=bug_fix.md` to your pull request URL. -->
# Description
<!-- Describe the new feature or modification to an existing feature clearly and consciously. -->
# Motivation
<!-- Explain the reason for adding or modifying this feature. -->
# Key changes
<!-- Provide a technically detailed description of the key changes made. -->
- Frontend
- Backend
# Test plan
## Suggestions
<!-- Provide any suggestions or recommendations for improvements in the testing plan. -->
## Underlying risk
<!-- Identify any potential risks or issues that may arise from the new feature or modification. -->
# Showcase
<!-- Including any screenshots of the new feature or modification. -->
Co-authored-by: sealday <sealday@gmail.com>
Co-authored-by: bai.jingfeng <bai.jingfeng@foxmail.com>
Reviewed-on: daoyoucloud/tachycode#486
Co-authored-by: wjh <wwwjh0710@163.com>
Co-committed-by: wjh <wwwjh0710@163.com>
