Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / form-atoms/field issues and pull requests
#100 - Add `debugLabel` to internal atoms of `listAtom`
Issue -
State: closed - Opened by MiroslavPetrik 10 months ago
- 1 comment
#100 - Add `debugLabel` to internal atoms of `listAtom`
Issue -
State: closed - Opened by MiroslavPetrik 10 months ago
- 1 comment
#100 - Add `debugLabel` to internal atoms of `listAtom`
Issue -
State: closed - Opened by MiroslavPetrik 10 months ago
- 1 comment
#99 - Label key rendering SSR vs client atom id mismatch
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#99 - Label key rendering SSR vs client atom id mismatch
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#99 - Label key rendering SSR vs client atom id mismatch
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#98 - fix: make fields initializable
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#98 - fix: make fields initializable
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#98 - fix: make fields initializable
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#97 - fix(useMultiSelectFieldProps): make field initializable via options (…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#97 - fix(useMultiSelectFieldProps): make field initializable via options (…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#97 - fix(useMultiSelectFieldProps): make field initializable via options (…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#96 - make multiselect initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#96 - make multiselect initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#95 - fix(useCheckboxGroup): make field initializable (#94)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#95 - fix(useCheckboxGroup): make field initializable (#94)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#94 - Make checkboxGroup initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#94 - Make checkboxGroup initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#94 - Make checkboxGroup initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#93 - fix(RadioGroup): support for `initialValue` prop (#92)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#93 - fix(RadioGroup): support for `initialValue` prop (#92)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#93 - fix(RadioGroup): support for `initialValue` prop (#92)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#92 - make radio initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#92 - make radio initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#92 - make radio initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#91 - fix(useSelectFieldProps): make field initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#91 - fix(useSelectFieldProps): make field initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#91 - fix(useSelectFieldProps): make field initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#90 - make select initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#90 - make select initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#90 - make select initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#89 - fix(useTextFieldProps): make textField initializable via options (#88)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#89 - fix(useTextFieldProps): make textField initializable via options (#88)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#89 - fix(useTextFieldProps): make textField initializable via options (#88)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#88 - make textField initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#88 - make textField initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#88 - make textField initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next, released
#87 - fix(useFilesFieldProps): ignore the initialValue (#86)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#87 - fix(useFilesFieldProps): ignore the initialValue (#86)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#87 - fix(useFilesFieldProps): ignore the initialValue (#86)
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#86 - make fileField not initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#86 - make fileField not initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#86 - make fileField not initializable
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#85 - fix(useNumberFieldProps): make numberField initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#85 - fix(useNumberFieldProps): make numberField initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#84 - 81 enable passing initialvalue to usefieldprops
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#84 - 81 enable passing initialvalue to usefieldprops
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#84 - 81 enable passing initialvalue to usefieldprops
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#83 - fix(checkboxFieldProps): make checkboxField initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#83 - fix(checkboxFieldProps): make checkboxField initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#83 - fix(checkboxFieldProps): make checkboxField initializable via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#82 - fix(useFieldProps): enable passing initialValue via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#82 - fix(useFieldProps): enable passing initialValue via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#82 - fix(useFieldProps): enable passing initialValue via options
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released on @next
#81 - Enable passing `initialValue` to `useFieldProps`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#81 - Enable passing `initialValue` to `useFieldProps`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#80 - fix(listAtom): compute the dirty flag
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#80 - fix(listAtom): compute the dirty flag
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#80 - fix(listAtom): compute the dirty flag
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#79 - Make `dirtyAtom` of `listAtom` dependent on the array value
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#79 - Make `dirtyAtom` of `listAtom` dependent on the array value
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#79 - Make `dirtyAtom` of `listAtom` dependent on the array value
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#78 - fix: reuse `formAtom._validateFields`
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#78 - fix: reuse `formAtom._validateFields`
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#78 - fix: reuse `formAtom._validateFields`
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#77 - fix: use hydrateAtoms for listField
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released
#77 - fix: use hydrateAtoms for listField
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released
#77 - fix: use hydrateAtoms for listField
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released
#76 - Next
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#76 - Next
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#76 - Next
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#75 - fix(listAtom): validate controls listErrors & calls nested form valid…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#75 - fix(listAtom): validate controls listErrors & calls nested form valid…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#75 - fix(listAtom): validate controls listErrors & calls nested form valid…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#74 - fix(listField): use ListAtomConfig with the invalidItemError
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#74 - fix(listField): use ListAtomConfig with the invalidItemError
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#74 - fix(listField): use ListAtomConfig with the invalidItemError
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released on @next
#73 - `listField` config types does not include `invalidItemError`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, good first issue
#73 - `listField` config types does not include `invalidItemError`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, good first issue
#73 - `listField` config types does not include `invalidItemError`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, good first issue
#72 - listAtom validate action should update the `listErrorAtom`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, released on @next
#72 - listAtom validate action should update the `listErrorAtom`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, released on @next
#72 - listAtom validate action should update the `listErrorAtom`
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, released on @next
#71 - 68 the validateatom of listatom should listen to the validation of inner fields
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
#71 - 68 the validateatom of listatom should listen to the validation of inner fields
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
#71 - 68 the validateatom of listatom should listen to the validation of inner fields
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
#70 - 68 the validateatom of listatom should listen to the validation of in…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#70 - 68 the validateatom of listatom should listen to the validation of in…
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#69 - 68 the validateatom of listatom should listen to the validation of inner fields
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#69 - 68 the validateatom of listatom should listen to the validation of inner fields
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
#68 - the `validateAtom` of `listAtom` should listen to the validation of inner fields
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#68 - the `validateAtom` of `listAtom` should listen to the validation of inner fields
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#68 - the `validateAtom` of `listAtom` should listen to the validation of inner fields
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
#67 - chore(vite): update & cleanup
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#67 - chore(vite): update & cleanup
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: released
#66 - props from useNumberFieldProps have string value
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, good first issue
#66 - props from useNumberFieldProps have string value
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, good first issue
#66 - props from useNumberFieldProps have string value
Issue -
State: closed - Opened by MiroslavPetrik 11 months ago
- 1 comment
Labels: bug, good first issue
#65 - Next
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released
#65 - Next
Pull Request -
State: closed - Opened by MiroslavPetrik 11 months ago
- 2 comments
Labels: released