pablo-abc/felte issues and pull requests

#174 - initialValues doesn't update DOM correctly for <select> elements with <option value="...">

Issue - State: closed - Opened by level2-alejandro about 2 years ago - 3 comments
Labels: bug

#174 - initialValues doesn't update DOM correctly for <select> elements with <option value="...">

Issue - State: closed - Opened by level2-alejandro about 2 years ago - 3 comments
Labels: bug

#174 - initialValues doesn't update DOM correctly for <select> elements with <option value="...">

Issue - State: closed - Opened by level2-alejandro about 2 years ago - 3 comments
Labels: bug

#174 - initialValues doesn't update DOM correctly for <select> elements with <option value="...">

Issue - State: closed - Opened by level2-alejandro about 2 years ago - 3 comments
Labels: bug

#174 - initialValues doesn't update DOM correctly for <select> elements with <option value="...">

Issue - State: closed - Opened by level2-alejandro about 2 years ago - 3 comments
Labels: bug

#174 - initialValues doesn't update DOM correctly for <select> elements with <option value="...">

Issue - State: closed - Opened by level2-alejandro about 2 years ago - 3 comments
Labels: bug

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#173 - setErrors not working with server side errors.

Issue - State: closed - Opened by inder2303 about 2 years ago - 2 comments

#172 - Initial data with optional types becomes non-optional

Issue - State: open - Opened by kevinrenskers about 2 years ago - 2 comments
Labels: enhancement

#172 - Initial data with optional types becomes non-optional

Issue - State: open - Opened by kevinrenskers about 2 years ago - 2 comments
Labels: enhancement

#172 - Initial data with optional types becomes non-optional

Issue - State: open - Opened by kevinrenskers about 2 years ago - 2 comments
Labels: enhancement

#172 - Initial data with optional types becomes non-optional

Issue - State: open - Opened by kevinrenskers about 2 years ago - 2 comments
Labels: enhancement

#172 - Initial data with optional types becomes non-optional

Issue - State: open - Opened by kevinrenskers about 2 years ago - 2 comments
Labels: enhancement

#171 - types from `svelte/store` is required even for react project

Issue - State: closed - Opened by stregouet about 2 years ago - 2 comments
Labels: bug

#171 - types from `svelte/store` is required even for react project

Issue - State: closed - Opened by stregouet about 2 years ago - 2 comments
Labels: bug

#171 - types from `svelte/store` is required even for react project

Issue - State: closed - Opened by stregouet about 2 years ago - 2 comments
Labels: bug

#171 - types from `svelte/store` is required even for react project

Issue - State: closed - Opened by stregouet about 2 years ago - 2 comments
Labels: bug

#171 - types from `svelte/store` is required even for react project

Issue - State: closed - Opened by stregouet about 2 years ago - 2 comments
Labels: bug

#171 - types from `svelte/store` is required even for react project

Issue - State: closed - Opened by stregouet about 2 years ago - 2 comments
Labels: bug

#168 - Felte does not store checkbox `value` attribute properly.

Issue - State: closed - Opened by jchatard about 2 years ago - 1 comment
Labels: bug

#168 - Felte does not store checkbox `value` attribute properly.

Issue - State: closed - Opened by jchatard about 2 years ago - 1 comment
Labels: bug

#168 - Felte does not store checkbox `value` attribute properly.

Issue - State: closed - Opened by jchatard about 2 years ago - 1 comment
Labels: bug

#168 - Felte does not store checkbox `value` attribute properly.

Issue - State: closed - Opened by jchatard about 2 years ago - 1 comment
Labels: bug

#166 - "Type instantiation is excessively deep and possibly infinite" with Zod validator

Issue - State: open - Opened by pzuraq about 2 years ago - 1 comment
Labels: bug

#166 - "Type instantiation is excessively deep and possibly infinite" with Zod validator

Issue - State: open - Opened by pzuraq about 2 years ago - 1 comment
Labels: bug

#166 - "Type instantiation is excessively deep and possibly infinite" with Zod validator

Issue - State: open - Opened by pzuraq about 2 years ago - 1 comment
Labels: bug

#166 - "Type instantiation is excessively deep and possibly infinite" with Zod validator

Issue - State: open - Opened by pzuraq about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#165 - multipart/form-data should not contain content-type header

Issue - State: closed - Opened by lulucas about 2 years ago - 1 comment
Labels: bug

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#164 - Transform function type should, at least preserve the shape of the Data

Issue - State: open - Opened by danielo515 about 2 years ago - 3 comments

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: closed - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: closed - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: closed - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: closed - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: closed - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug

#163 - Passing onBlur to an input clears the value when the blur event happens

Issue - State: open - Opened by danielo515 about 2 years ago
Labels: bug