Skip to content

Releases: viclafouch/mui-color-input

v7.0.0

17 Apr 18:40
Compare
Choose a tag to compare

Feat

  • Upgrade to MUI v7
  • Eslint 9
  • Update deps

v6.0.0

07 Mar 10:20
Compare
Choose a tag to compare

Feature

  • Enable compatibility with React 19 (React 18 is still maintained).
  • Update deps

No breaking change.

v5.0.1

09 Nov 17:27
Compare
Choose a tag to compare

Fixes

  • #44 We removed type: "module" from package.json file. Let's try this for now.

v5.0.0

09 Nov 17:08
Compare
Choose a tag to compare

🚨 BREAKING CHANGE

  • Upgrade to MUI V6 ONLY. V5 is no more compatible. If you want more features and bug fixes from this package, you should consider upgrade your codebase to V6.

Features

  • #50 ColorButton is exported as MuiColorInputButton.

v4.0.2

18 Oct 21:52
Compare
Choose a tag to compare

Chore

  • Update deps

v4.0.1

21 Sep 10:31
Compare
Choose a tag to compare

Chore

  • Update dependencies
  • Add type="module" to package.json file
  • Add check types step with @arethetypeswrong/cli and fix issues.

v4.0.0

29 Aug 09:45
Compare
Choose a tag to compare

Feat

  • Compatibility with MUI V6 (and still with V5).
  • Update deps

v3.0.0

07 Jul 10:32
Compare
Choose a tag to compare

Fixes

  • #36 onChange is not called with invalid value

What does it mean ?

Now, if you don't provide any fallback value with the fallbackValue prop, mui-color-input will not force the value to be a color when you blur the element.

Also, onChange can give you an invalid color value. You can still check if it's valid with matchIsValidColor function.

v2.0.3

19 Feb 14:49
Compare
Choose a tag to compare

Fixes

v2.0.2

13 Feb 17:14
Compare
Choose a tag to compare

Chore

  • Update deps