UNPKG

3.79 kBMarkdownView Raw
1# Changelog
2
3All notable changes to this project will be documented in this file.
4
5The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
6and adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
7
8<!-- ## [Unreleased] -->
9
10## [0.11.11] - 2019-10-01
11
12### Added
13
14- new `asChoiceField` utility function to support `Checkbox` and `RadioButton` [#1070](https://github.com/Shopify/quilt/pull/1070)
15
16## [0.11.8] - 2019-08-29
17
18### Fixed
19
20- Fixed using multiple layers deep of nested `<List />` inside of `<List />`
21
22## [0.11.3]
23
24### Added
25
26- Extend the return type of the submit handler for `FormState` component to accept a promise of both `void` and `RemoteError[]`. [#736](https://github.com/Shopify/quilt/pull/736)
27
28## [0.11.2] - 2019-05-22
29
30### Fixed
31
32- validator signatures produced by `validate()` no longer require a `fields` param. [#714](https://github.com/Shopify/quilt/pull/714)
33
34## [0.11.1] - 2019-05-15
35
36### Fixed
37
38- `FormState.Nested` no longer breaks when used in a `FormState.List` and an item is added [#698](https://github.com/Shopify/quilt/pull/698)
39
40## [0.10.0]
41
42### Changed
43
44- when `validateOnSubmit` is enabled, validation errors are surfaced on the form's `errors`. [#601](https://github.com/Shopify/quilt/pull/601)
45
46## [0.9.1]
47
48### Changed
49
50- `isNumeric` function ReGex now matches for negative numbers. This impacts users of `isNumericString` validator function relying on its previous behaviour of only allowing positive numbers. To reintroduce that behaviour please use `isPostiveNumericString`
51
52## [0.9.0]
53
54### Removed
55
56- `<Nested />` and `<List />`: removed logic in `shouldComponentUpdate()` limiting updates
57
58## [0.8.0]
59
60### Added
61
62- You can now provide `externalErrors` to the `FormState` component to be merged into the form's `error` objects.
63
64### Changed
65
66- lodash is no longer used internally. [#475](https://github.com/Shopify/quilt/pull/475)
67
68### Fixed
69
70- Fixes validators for cases where `externalErrors` are not provided. [#504](https://github.com/Shopify/quilt/pull/504)
71
72## [0.7.0]
73
74### Added
75
76- You can now use the onInitialValueChanged prop with fields having nested properties. [#464](https://github.com/Shopify/quilt/pull/464)
77
78### Fixed
79
80- `submit` now checks for the existence of `preventDefault` on the event passed in before calling it. [#465](https://github.com/Shopify/quilt/pull/465)
81
82## [0.6.0]
83
84### Added
85
86- You can control how `<FormState />` reacts to changes in the initialValue prop using onInitialValueChanged.
87
88## [0.5.0]
89
90### Added
91
92- `<List />` supports `getChildKey` to provide custom `key`s for it's children. [#387](https://github.com/Shopify/quilt/pull/387)
93
94## [0.4.1]
95
96### Fixed
97
98- `<List />` no longer breaks on name generation.
99
100## [0.4.0]
101
102### Added
103
104- The `validateRequired` helper can be used to generate validators that run even on empty input.
105
106## [0.3.3]
107
108### Fixed
109
110- Validators that depend on `FieldState` have more robust typing.
111
112## [0.3.2]
113
114### Fixed
115
116- When validators fail during a submit submitting is reset to false.
117
118## [0.3.0]
119
120### Added
121
122- The `validateOnSubmit` prop can be used to have validators run before the `onSubmit` function is called and will prevent `onSubmit` from being called if any fail.
123
124## [0.2.10]
125
126### Fixed
127
128- Fixed using multiple layers deep of Nested and List breaking the state.
129
130## [0.2.9]
131
132### Fixed
133
134- No longer accidentally import all of lodash.
135
136## [0.2.8]
137
138### Changed
139
140- Validators based on `validate` now always succeed for an empty input. The `required` and `requiredString` validators continue to behave the same way they used to.
141
142### Fixed
143
144- Fixed Nested and List component race condition. Nested and List now pass a function to their `onChange` prop instead of an object so that the data object will be created within `setState`.