Releases: razorpay/blade
Releases · razorpay/blade
@razorpay/blade@12.13.1
Patch Changes
- 3739287: feat(blade): add should showNavigationButtons prop in carousel
@razorpay/blade@12.13.0
Minor Changes
- 1911962: feat(blade): add drag handle icon
@razorpay/blade@12.12.1
@razorpay/blade@12.12.0
Minor Changes
- 7e155b6: feat(blade): add engage and translate icons
@razorpay/blade@12.11.0
Minor Changes
- d906838: feat(blade): add Chat Message component
@razorpay/blade@12.10.0
@razorpay/blade@12.9.1
@razorpay/blade@12.9.0
Minor Changes
- e035b38: feat(DropdownIconButton): add support for DropdownIconButton and tooltip for Dropdown triggers
@razorpay/blade@12.8.2
Patch Changes
-
3be3f0f: fix(FileUpload): revert to not calling onChange on file remove
[!NOTE]
Check the below timeline if you're upgrading from 11.34.1+ version to this version
Timeline of FileUpload changes
- In 11.34.1: We did not call onChange on removing of file. Only onRemove was called
- In 11:36.2: We added dispatchEvent call which started calling onChange on onRemove (since React treats
input type="file"
differently thaninput type="text"
- CodeSandbox Link) - In 12.4.0: We released a fix thinking onChange call was expected behaviour and we just updated the state value for it
- This version: Reverts back to 11.34.1 behaviour. If you're upgrading to this version from 11.34.1 or previous versions, the behaviour will stay same. If you're upgrading from 11.34.1+ and use FileUpload component, its recommended to test out FileUpload instances.
-
3c040f6: feat: add icon only chip
@razorpay/blade@11.40.3
Patch Changes
-
e50729d: fix(FileUpload): revert to not calling onChange on file remove
[!NOTE]
Check the below timeline if you're upgrading from 11.34.1+ version to this version
Timeline of FileUpload changes
- In 11.34.1: We did not call onChange on removing of file. Only onRemove was called
- In 11:36.2: We added dispatchEvent call which started calling onChange on onRemove (since React treats
input type="file"
differently thaninput type="text"
- CodeSandbox Link) - In 12.4.0: We released a fix thinking onChange call was expected behaviour and we just updated the state value for it
- This version: Reverts back to 11.34.1 behaviour. If you're upgrading to this version from 11.34.1 or previous versions, the behaviour will stay same. If you're upgrading from 11.34.1+ and use FileUpload component, its recommended to test out FileUpload instances.