fc302ec4a5
This PR adds some unit tests for the camera constraints API I took educated guesses at the intended panning and zoom behaviour for the editor's constraints. But I couldn't work out what the intended behaviour was for a couple of the tests, so I've left these ones for now: ```javascript describe('Allows mixed values for x and y', () => { it.todo('Allows different values to be set for x and y axes') }) ``` ```javascript describe('Contain behavior', () => { it.todo( 'Locks axis until the bounds are bigger than the padded viewport, then allows "inside" panning' ) }) ``` I also edited some earlier tests so they now use chaining, to be consistent with the other tests and hopefully easier to read. ### Change Type <!-- ❗ Please select a 'Scope' label ❗️ --> - [ ] `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 - [x] `internal` — Does not affect user-facing stuff <!-- ❗ Please select a 'Type' label ❗️ --> - [ ] `bugfix` — Bug fix - [ ] `feature` — New feature - [ ] `improvement` — Improving existing features - [ ] `chore` — Updating dependencies, other boring stuff - [ ] `galaxy brain` — Architectural changes - [x] `tests` — Changes to any test code - [ ] `tools` — Changes to infrastructure, CI, internal scripts, debugging tools, etc. - [ ] `dunno` — I don't know ### Test Plan 1. Add a step-by-step description of how to test your PR here. 2. - [ ] Unit Tests - [ ] End to end tests ### Release Notes - Adds tests for the camera constraints api |
||
---|---|---|
.. | ||
assets | ||
dotcom-shared | ||
editor | ||
namespaced-tldraw | ||
state | ||
store | ||
tldraw | ||
tlschema | ||
tlsync | ||
utils | ||
validate |