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

fix(listAtom): validate controls listErrors & calls nested form valid… #75

Conversation

MiroslavPetrik
Copy link
Member

…ation

Introducing useListActions as a refactor for the bulky useListField.
close #72

Copy link

codecov bot commented Jan 14, 2024

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (9e181f3) 89.80% compared to head (ef3c0a6) 90.00%.
Report is 4 commits behind head on next.

❗ Current head ef3c0a6 differs from pull request most recent head 467d00d. Consider uploading reports for the commit 467d00d to get more accurate results

Files Patch % Lines
src/atoms/list-atom/listAtom.ts 98.55% 2 Missing ⚠️
src/atoms/index.ts 0.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             next      #75      +/-   ##
==========================================
+ Coverage   89.80%   90.00%   +0.19%     
==========================================
  Files          86       89       +3     
  Lines        2158     2191      +33     
  Branches      177      181       +4     
==========================================
+ Hits         1938     1972      +34     
+ Misses        218      216       -2     
- Partials        2        3       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@MiroslavPetrik MiroslavPetrik force-pushed the 72-listatom-validate-action-should-update-the-listerroratom branch from ef3c0a6 to 467d00d Compare January 14, 2024 10:24
@MiroslavPetrik MiroslavPetrik merged commit d011313 into next Jan 14, 2024
1 check passed
github-actions bot pushed a commit that referenced this pull request Jan 14, 2024
## [4.0.2-next.2](v4.0.2-next.1...v4.0.2-next.2) (2024-01-14)

### Bug Fixes

* **listAtom:** validate controls listErrors ([#72](#72)) ([#75](#75)) ([d011313](d011313))
Copy link

🎉 This PR is included in version 4.0.2-next.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

MiroslavPetrik added a commit that referenced this pull request Jan 14, 2024
* fix(listField): use ListAtomConfig with the invalidItemError (#74)

* chore(release): 4.0.2-next.1

## [4.0.2-next.1](v4.0.1...v4.0.2-next.1) (2024-01-14)

### Bug Fixes

* **listField:** use ListAtomConfig with the invalidItemError ([#74](#74)) ([6d28e0d](6d28e0d))

* fix(listAtom): validate controls listErrors (#72) (#75)

* chore(release): 4.0.2-next.2

## [4.0.2-next.2](v4.0.2-next.1...v4.0.2-next.2) (2024-01-14)

### Bug Fixes

* **listAtom:** validate controls listErrors ([#72](#72)) ([#75](#75)) ([d011313](d011313))

---------

Co-authored-by: semantic-release-bot <[email protected]>
@MiroslavPetrik MiroslavPetrik deleted the 72-listatom-validate-action-should-update-the-listerroratom branch January 14, 2024 10:28
MiroslavPetrik added a commit that referenced this pull request Jan 14, 2024
* fix(listField): use ListAtomConfig with the invalidItemError (#74)

* chore(release): 4.0.2-next.1

## [4.0.2-next.1](v4.0.1...v4.0.2-next.1) (2024-01-14)

### Bug Fixes

* **listField:** use ListAtomConfig with the invalidItemError ([#74](#74)) ([6d28e0d](6d28e0d))

* fix(listAtom): validate controls listErrors (#72) (#75)

* chore(release): 4.0.2-next.2

## [4.0.2-next.2](v4.0.2-next.1...v4.0.2-next.2) (2024-01-14)

### Bug Fixes

* **listAtom:** validate controls listErrors ([#72](#72)) ([#75](#75)) ([d011313](d011313))

---------

Co-authored-by: semantic-release-bot <[email protected]>
github-actions bot pushed a commit that referenced this pull request Jan 14, 2024
## [4.0.2](v4.0.1...v4.0.2) (2024-01-14)

### Bug Fixes

* release ([#76](#76)) ([#74](#74)) ([0cc383f](0cc383f)), closes [#72](#72) [#75](#75) [#72](#72) [#75](#75)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant