started

orhanoksuzz started alibaba/hooks

started time in 1 hour ago

started

oxinosg started alibaba/hooks

started time in 2 hours ago

push

janryWang push alibaba/formily

janryWang

commit time in 3 hours ago

fix(next): fix Space align is not work (#2531)

commit sha： 3f4afef1268f6240c2c44d2f0a486b07680e3512

push time in 3 hours ago

delete

janryWang in alibaba/formily delete branch fix_next_space_align

deleted time in 3 hours ago

pull request

janryWang pull request alibaba/formily

janryWang

janryWang COLLABORATOR

createdAt 3 hours ago

fix(next): fix Space align is not work

Before submitting a pull request, please make sure the following is done...

Ensure the pull request title and commit message follow the Commit Specific in English.
Fork the repo and create your branch from master or formily_next.
[] If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure the test suite passes (npm test).
Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

Please do not delete the above content

What have you changed?

Fixed #2527

issue

janryWang issue alibaba/formily

janryWang

janryWang NONE

createdAt 3 hours ago

[Bug Report] Space 组件布局 align 属性不起作用

I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce

使用 @formily/next 的 space 组件布局
设置如下属性：

direction: "vertical"

align: "start"
align: "start" 不起作用，实际效果为 center

What is expected?

align: "start"，实际效果与配置一致

What is actually happening?

align: "start" 配置不起作用

Package

@formily/[email protected] @formily/[email protected]

issue

github-actions[bot] issue comment alibaba/formily

github-actions[bot]

github-actions[bot] COLLABORATOR

createdAt 3 hours ago

fix(next): fix Space align is not work

Before submitting a pull request, please make sure the following is done...

Ensure the pull request title and commit message follow the Commit Specific in English.
Fork the repo and create your branch from master or formily_next.
[] If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure the test suite passes (npm test).
Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

Please do not delete the above content

What have you changed?

Fixed #2527

github-actions[bot]

comment in 3 hours ago

Size Change: +10 B (0%)

Total Size: 456 kB

Filename	Size	Change
`packages/next/dist/formily.next.umd.development.js`	65.1 kB	+3 B (0%)
`packages/next/dist/formily.next.umd.production.js`	38.6 kB	+7 B (0%)

ℹ️ View Unchanged

Filename	Size
`packages/antd/dist/formily.antd.umd.development.js`	60 kB
`packages/antd/dist/formily.antd.umd.production.js`	34.4 kB
`packages/core/dist/formily.core.umd.development.js`	19.3 kB
`packages/core/dist/formily.core.umd.production.js`	13.1 kB
`packages/element/dist/formily.element.umd.development.js`	58.3 kB
`packages/element/dist/formily.element.umd.production.js`	33.8 kB
`packages/grid/dist/formily.grid.umd.development.js`	4.81 kB
`packages/grid/dist/formily.grid.umd.production.js`	3.44 kB
`packages/json-schema/dist/formily.json-schema.umd.development.js`	6.85 kB
`packages/json-schema/dist/formily.json-schema.umd.production.js`	4.33 kB
`packages/path/dist/formily.path.umd.development.js`	11.1 kB
`packages/path/dist/formily.path.umd.production.js`	7.66 kB
`packages/react/dist/formily.react.umd.development.js`	11.3 kB
`packages/react/dist/formily.react.umd.production.js`	7.03 kB
`packages/reactive-react/dist/formily.reactive-react.umd.development.js`	3.61 kB
`packages/reactive-react/dist/formily.reactive-react.umd.production.js`	2.25 kB
`packages/reactive-vue/dist/formily.reactive-vue.umd.development.js`	2.86 kB
`packages/reactive-vue/dist/formily.reactive-vue.umd.production.js`	1.81 kB
`packages/reactive/dist/formily.reactive.umd.development.js`	9.08 kB
`packages/reactive/dist/formily.reactive.umd.production.js`	5.2 kB
`packages/shared/dist/formily.shared.umd.development.js`	7.39 kB
`packages/shared/dist/formily.shared.umd.production.js`	4.19 kB
`packages/validator/dist/formily.validator.umd.development.js`	8.38 kB
`packages/validator/dist/formily.validator.umd.production.js`	6.23 kB
`packages/vue/dist/formily.vue.umd.development.js`	16.1 kB
`packages/vue/dist/formily.vue.umd.production.js`	9.61 kB

_{compressed-size-action}

issue

codecov[bot] issue comment alibaba/formily

codecov[bot]

codecov[bot] COLLABORATOR

createdAt 3 hours ago

fix(next): fix Space align is not work

Before submitting a pull request, please make sure the following is done...

Ensure the pull request title and commit message follow the Commit Specific in English.
Fork the repo and create your branch from master or formily_next.
[] If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure the test suite passes (npm test).
Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

Please do not delete the above content

What have you changed?

Fixed #2527

codecov[bot]

comment in 3 hours ago

Codecov Report

Merging #2531 (7a11191) into formily_next (432f620) will increase coverage by 0.00%. The diff coverage is n/a.

@@              Coverage Diff              @@
##           formily_next    #2531   +/-   ##
=============================================
  Coverage         95.65%   95.66%           
=============================================
  Files               141      141           
  Lines              6313     6317    +4     
  Branches           1719     1720    +1     
=============================================
+ Hits               6039     6043    +4     
  Misses              243      243           
  Partials             31       31

Impacted Files	Coverage Δ
packages/reactive/src/array.ts	`100.00% <0.00%> (ø)`

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 432f620...7a11191. Read the comment docs.

started

dugujiutian2 started alibaba/p3c

started time in 3 hours ago

pull request

janryWang pull request alibaba/formily

janryWang

janryWang COLLABORATOR

createdAt 3 hours ago

fix(next): fix Space align is not work

Before submitting a pull request, please make sure the following is done...

Ensure the pull request title and commit message follow the Commit Specific in English.
Fork the repo and create your branch from master or formily_next.
[] If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure the test suite passes (npm test).
Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.