6dd6f8e77e
We allowed the users to customize pretty much all of our components, but not the `DebugPanel`. We had overrides for `DebugMenu` which is displayed inside the panel, but not for the panel itself. I guess it makes sense to allow users to override both?  Reported [here](https://discord.com/channels/859816885297741824/1221663945627140157/1221663945627140157). Fixes https://github.com/tldraw/tldraw/issues/3260 ### Change Type <!-- ❗ Please select a 'Scope' label ❗️ --> - [x] `sdk` — Changes the tldraw SDK - [ ] `dotcom` — Changes the tldraw.com web app - [ ] `docs` — Changes to the documentation, examples, or templates. - [ ] `vs code` — Changes to the vscode plugin - [ ] `internal` — Does not affect user-facing stuff <!-- ❗ Please select a 'Type' label ❗️ --> - [ ] `bugfix` — Bug fix - [x] `feature` — New feature - [ ] `improvement` — Improving existing features - [ ] `chore` — Updating dependencies, other boring stuff - [ ] `galaxy brain` — Architectural changes - [ ] `tests` — Changes to any test code - [ ] `tools` — Changes to infrastructure, CI, internal scripts, debugging tools, etc. - [ ] `dunno` — I don't know ### Test Plan 1. Best way to test this is to check the `Hidden UI Components` example. 2. Play around with commenting out the `DebugPanel` and `DebugMenu` overrides. - [ ] Unit Tests - [ ] End to end tests ### Release Notes - Allow users to fully override the `DebugPanel`. |
||
|---|---|---|
| .. | ||
| assets | ||
| editor | ||
| namespaced-tldraw | ||
| state | ||
| store | ||
| tldraw | ||
| tlschema | ||
| tlsync | ||
| utils | ||
| validate | ||