bdbch
bdbch
I put it back into our 2.0.0 Release Milestone.
@OliverGrimsley what warnings are thrown?
LGTM for now – feel free to add docs to the PR
@tonyhallett I moved your commit over to #5838 and added a little bit on top. Closing this PR for that.
Looks good from my side then and can be merged. Feel free @nperez0111
 We could do something like this maybe? But I also think a copy change could work as well. Wasn't sure myself when I made those changes but guessed people...
I'd let the maintainers decide if the current implementation is fine or design or copy changes are required 👍 but I'm open to make any changes.
Agreeing with a change like that being confusing without changing it's design or the copy around it. I think the most confusing part is the copy presenting it "Here's your...
Closing this for now as I wasn't able to replicate the issue in #4417 - if someone could provide a Codesandbox with this issue still being in the more recent...
Could you give us a step to replicate this? I'd like to take a look into it.