Track/1.0

[jannikbuschke]

A PR to track the remaining work for a 1.0 release

• Find solution/recommendation whether to use <form> and native button type attributes
• Add Cascader
• Add TreeSelect
• Add Mention
• Add AutoComplete
• Create a pre-release

[joshsmith]

As part of 1.0 are you planning on having labels work? Currently, I believe that setting name is causing labels to be broken and not know what the for should be.

[jannikbuschke]

Can you elaborate a bit which labels you mean exactly?

[joshsmith]

Can you elaborate a bit which labels you mean exactly?

Sure, here's a forked example of your CodeSandbox: https://codesandbox.io/s/y257p4l8z9

Edit: as a counter-example, look at antd's own CodeSandbox to see how the DOM differs: https://codesandbox.io/s/kw79qx5w15

The label element for [name=userName] does not have a for="userName", which breaks things like react-testing-library's getByLabelText and forces me to fallback to less optimal methods for finding and filling inputs, and breaks some browser / a11y behavior.

I have a feeling this is some sort of props issue, but honestly just have not had time to examine further.

(P.S. Thanks for making this!)

[jannikbuschke]

That is some cool input. Testing (especially with react-testing-library) and a11y stuff should definitely be fixed. Im not sure how much effort it will be, and it does not necessarily need to be part of the 1.0 release. Im also fine moving forward to a 2.0 release if it makes sense, or fix things as part of 1.* releases.

[jannikbuschke]

accidentally merged. Recreated: #29