Skip to content
This repository has been archived by the owner on Mar 1, 2024. It is now read-only.

fix(Form): Fix invalid properties for maxLength, minLength, autoComplete #440

Merged
merged 1 commit into from
May 31, 2019

Conversation

akabraham
Copy link
Contributor

Fix maxLength, minLength, autoComplete "Invalid DOM property" errors for Form element.

Fixes #434

@levino
Copy link

levino commented Apr 29, 2019

Please merge this ASAP!

@nating
Copy link
Contributor

nating commented May 13, 2019

Any chance of getting this merged and released, @AaronCoplan ? Our console would be eternally grateful! 😬

Copy link
Contributor

@joaquinwojcik joaquinwojcik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent. It should be merged ASAP.

@akabraham
Copy link
Contributor Author

Who has the ability to merge this?

@blackstorm
Copy link

@akabraham I think no one. Please plan B

@levino
Copy link

levino commented May 21, 2019

I meanwhile found that the library is badly designed overall (try to implement a logout button in the accounts dropdown). I use antd now.

Copy link

@wolph wolph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tested this in Firefox and Chrome. The only issue I see is that it changes the autocomplete parameter to <Form> to autoComplete which can break peoples' code

@nating
Copy link
Contributor

nating commented May 23, 2019

@jonthomp Any chance of a merge / release of this? 😅

@jonthomp
Copy link
Contributor

Sorry all I've been away for the last 4 weeks, updates, PR merging etc incoming...

@jonthomp
Copy link
Contributor

As it stands this should be a breaking change release unless we also keep the old props? Any thoughts/opinions on this?

@wolph
Copy link

wolph commented May 31, 2019

It's indeed a breaking change but fixing it is a one-off. I would assume that the manual parameters don't get much use in any case.

It might be neater to support both but I believe it's a non-issue

@hasan-sytel
Copy link

I think we should replace with camelCase as react requires camelCase, please see similar discussion in react repo: facebook/react#2882

@jonthomp jonthomp merged commit cb4a69a into tabler:master May 31, 2019
jonthomp pushed a commit that referenced this pull request Jun 1, 2019
# [1.30.0](v1.29.0...v1.30.0) (2019-06-01)

### Bug Fixes

* **Form:** Fix invalid properties for maxLength, minLength, autoComplete ([d63f9c3](d63f9c3))
* **Form:** Fix invalid properties for maxLength, minLength, autoComplete ([#440](#440)) ([cb4a69a](cb4a69a))
* **package:** update d3-scale to version 3.0.0 ([e927826](e927826))
* **package:** update react-router-dom to version 5.0.0 ([464eea4](464eea4))

### Features

* **FileInput:** add accept property ([0965e51](0965e51))
* **StandAloneFormPage:** Made the logo variable ([2d9d48e](2d9d48e))
@jonthomp
Copy link
Contributor

jonthomp commented Jun 1, 2019

🎉 This PR is included in version 1.30.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid DOM property minlength. Did you mean minLength