[Autocomplete] Remove debug in favor of open and dev tools

[eps1lon]

Breaking changes

• [Autocomplete] Remove debug prop
  There are a couple of simpler alternatives: open={true}, Chrome devtools "Emulate focused", or React devtools props.

---

With recent react-devtools updates editing props is fairly straight forward and more powerful than a non-descriptive debug prop that is even part of the prod bundle.

The uncontrolled case isn't as straight forward but you can always switch to controlled in your codebase

[mui-pr-bot]

Details of bundle changes

Generated by 🚫 dangerJS against 8815e90

[oliviertassinari]

The prop is most often used to customize the rendering of the popup, the CSS, or the elements themselves. During such a session, the solution needs to support fast refresh and likely hard reload. I would be cautious with a React dev-tools or a Chrome Devtool only solution because it has a short lifespan. One downside of the debug prop is its upside: it's persistent, it can end-up in production 😆. What do you think?

[eps1lon]

During such a session, the solution needs to support fast refresh and likely hard reload.

Set open={true} instead of debug then like you would with any other popup-like ui? It's about unifying the debug experience which should not be a footgun. debug ending up in production is highly problematic.

debug is a misleading term at the moment considering to what it applies.

[oliviertassinari]

Yeah ok, I will use open in the future. Great alternative! I originally got the idea from https://docsearch.algolia.com/docs/styling/#debugging.

I have added a diff for the next release changelog in the PR's description. What do you think about it? Could we include something in the v5 migration guide?