PrivateCoffee/tldraw
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
tldraw/.gitignore

104 lines
1.3 KiB
Text
Raw Permalink Normal View History

transfer-out: transfer out
2023-04-25 11:01:25 +00:00
# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
lerna-debug.log*
New migrations again (#3220) Describe what your pull request does. If appropriate, add GIFs or images showing the before and after. ### Change Type - [x] `sdk` — Changes the tldraw SDK - [x] `galaxy brain` — Architectural changes ### 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 #### BREAKING CHANGES - The `Migrations` type is now called `LegacyMigrations`. - The serialized schema format (e.g. returned by `StoreSchema.serialize()` and `Store.getSnapshot()`) has changed. You don't need to do anything about it unless you were reading data directly from the schema for some reason. In which case it'd be best to avoid that in the future! We have no plans to change the schema format again (this time was traumatic enough) but you never know. - `compareRecordVersions` and the `RecordVersion` type have both disappeared. There is no replacement. These were public by mistake anyway, so hopefully nobody had been using it. - `compareSchemas` is a bit less useful now. Our migrations system has become a little fuzzy to allow for simpler UX when adding/removing custom extensions and 3rd party dependencies, and as a result we can no longer compare serialized schemas in any rigorous manner. You can rely on this function to return `0` if the schemas are the same. Otherwise it will return `-1` if the schema on the right _seems_ to be newer than the schema on the left, but it cannot guarantee that in situations where migration sequences have been removed over time (e.g. if you remove one of the builtin tldraw shapes). Generally speaking, the best way to check schema compatibility now is to call `store.schema.getMigrationsSince(persistedSchema)`. This will throw an error if there is no upgrade path from the `persistedSchema` to the current version. - `defineMigrations` has been deprecated and will be removed in a future release. For upgrade instructions see https://tldraw.dev/docs/persistence#Updating-legacy-shape-migrations-defineMigrations - `migrate` has been removed. Nobody should have been using this but if you were you'll need to find an alternative. For migrating tldraw data, you should stick to using `schema.migrateStoreSnapshot` and, if you are building a nuanced sync engine that supports some amount of backwards compatibility, also feel free to use `schema.migratePersistedRecord`. - the `Migration` type has changed. If you need the old one for some reason it has been renamed to `LegacyMigration`. It will be removed in a future release. - the `Migrations` type has been renamed to `LegacyMigrations` and will be removed in a future release. - the `SerializedSchema` type has been augmented. If you need the old version specifically you can use `SerializedSchemaV1` --------- Co-authored-by: Steve Ruiz <steveruizok@gmail.com>
2024-04-15 12:53:42 +00:00
.rooms
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
node_modules
dist
dist-cjs
dist-esm
.tsbuild*
.lazy
dist-ssr
*.local
# Editor directories and files
.vscode/*
!.vscode/extensions.json
.idea
.DS_Store
*.suo
*.ntvs*
*.njsproj
*.sln
*.sw?
# turborepo
.turbo
coverage
**/*.env
**/*.tsbuildinfo
**/*.css.map
**/*.js.map
apps/examples/www/index.js
apps/examples/www/index.css
nohup.out
packages/*/package
packages/*/*.tgz
tsconfig.build.json
.vercel
api-json
api-md
tldraw.css (#1607) This PR introduces `@tldraw/tldraw/tldraw.css`, an exported CSS file that replaces the `editor.css` and `ui.css` that were previously copied from the editor and ui packages. Instead, these files are combined into the `tldraw.css` file, simplifying the import story when using `@tldraw/tldraw`. ### Change Type - [x] `major` — Breaking change ### Release Notes - [tldraw] Removes `editor.css` and `ui.css` exports, replaces with `tldraw.css`
2023-06-17 22:33:21 +00:00
packages/tldraw/tldraw.css
Remove namespaced-tldraw/tldraw.css (#3068) This is a generated file that shouldn't be checked in. ### Change Type - [x] `internal` — Any other changes that don't affect the published package[^2]
2024-03-04 17:13:12 +00:00
packages/namespaced-tldraw/tldraw.css
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
packages/assets/embed-icons
packages/assets/fonts
packages/assets/icons
packages/assets/translations
apps/examples/www/embed-icons
apps/examples/www/fonts
apps/examples/www/icons
apps/examples/www/translations
# yarn v2
.pnp.*
.yarn/*
!.yarn/patches
!.yarn/plugins
!.yarn/releases
!.yarn/sdks
!.yarn/versions
Publish api.json (#2034) This PR publishes the api.json files created by the build-api scripts. ### Change Type - [x] `internal`
2023-10-08 15:00:58 +00:00
packages/*/api/temp
Don't check api.json files into git (#3565) These were needed when the docs lived in a different repo, but they don't any more so we can get rid of them. ### Change Type - [x] `internal` — Does not affect user-facing stuff - [x] `chore` — Updating dependencies, other boring stuff
2024-04-24 15:58:26 +00:00
packages/*/api/api.json
Publish api.json (#2034) This PR publishes the api.json files created by the build-api scripts. ### Change Type - [x] `internal`
2023-10-08 15:00:58 +00:00
packages/*/api/internal.d.ts
packages/*/api/public.d.ts
transfer-out: transfer out
2023-04-25 11:01:25 +00:00
apps/examples/www/index.css
apps/examples/www/index.js
.tsbuild
Added `pHYs` to import/export of png images (#1200) Added the following - Always export pngs with a pixel-ratio of `2` - Added the `pHYs` png metadata chunk describing the pixel ratio so it opens with the correct size - When importing PNGs read the `pHYs` chunk for the sizing info All the exporting is done via just modifying the bytes from the browsers native image handling. https://user-images.githubusercontent.com/235915/234309015-19f39f3a-66ce-4ec2-b7d0-b34a07ed346b.mov I've also added `ANALYZE=true` option to get the build metadata from esbuild on boot of `yarn dev` which allow me to see the bundle size info in https://esbuild.github.io/analyze/ ![esbuild github io_analyze_](https://user-images.githubusercontent.com/235915/234310302-c6fe8109-c82d-480a-8c65-c7638b09e71e.png) You can see that `crc` adds about `4.4kb` <img width="280" alt="Screenshot 2023-04-25 at 15 33 26" src="https://user-images.githubusercontent.com/235915/234310669-99e3e787-ddca-4ad2-81cf-b4a541631d62.png"> --------- Co-authored-by: Steve Ruiz <steveruizok@gmail.com>
2023-04-29 22:10:01 +00:00
apps/examples/build.esbuild.json
Added initial webdriver tests (#1337) Adds webdriver tests for testing from a users perspective via browser actions. We currently support local test runners for a bunch of actions on desktop `chrome`/`firefox`/`edge`/`safari` on macos. We also have a browserstack runner which we'll enable in another PR. ### Release Note - Adds initial webdriver tests
2023-05-09 20:21:45 +00:00
Add playwright tests (#1484) This PR replaces our webdriver end to end tests with playwright tests. It: - replaces our webdriver workflow with a new e2e workflow based on playwright - removes the webdriver project - adds e2e tests to our examples app - replaces all `data-wd` attributes with `data-testid` ### Coverage Most of the tests from our previous e2e tests are reproduced here, though there are some related to our gestures that will need to be done in a different way—or not at all. I've also added a handful of new tests, too. ### Where are they The tests are now part of our examples app rather than being in its own different app. This should help us test our different examples too. As far as I can tell there are no downsides here in terms of the regular developer experience, though they might complicate any CodeSandbox projects that are hooked into the examples app. ### Change Type - [x] `tests` — Changes to any testing-related code only (will not publish a new version)
2023-05-30 14:28:56 +00:00
apps/examples/e2e/test-results
untrack generated files (#1646) This PR untracks generated docs files. It does some minor repo cleanup. ### Change Type - [x] `internal`
2023-06-24 08:22:42 +00:00
apps/examples/playwright-report
[dx] add gen docs to gitignore (#2704) This PR ignores generated markdown files. ### Change Type - [x] `internal` — Any other changes that don't affect the published package[^2]
2024-02-01 15:06:37 +00:00
apps/docs/content/gen
Don't check api.json files into git (#3565) These were needed when the docs lived in a different repo, but they don't any more so we can get rid of them. ### Change Type - [x] `internal` — Does not affect user-facing stuff - [x] `chore` — Updating dependencies, other boring stuff
2024-04-24 15:58:26 +00:00
apps/docs/content/releases
apps/docs/api
unbrivate, dot com in (#2475) This PR moves the tldraw.com app into the public repo. ### Change Type - [x] `internal` — Any other changes that don't affect the published package[^2] --------- Co-authored-by: Dan Groshev <git@dgroshev.com> Co-authored-by: alex <alex@dytry.ch>
2024-01-16 14:38:05 +00:00
.dev.vars
.env.local
.env.development.local
.env*
.wrangler
[internal] Add license report scripts (#2751) This PR adds scripts that allow us to generate reports on our dependencies. ### Change Type - [x] `internal` — Any other changes that don't affect the published package[^2]
2024-04-01 13:36:40 +00:00
/vercel.json
license-report-prod.html
license-report.html
check worker bundle sizes (#4032) This PR aims to make sure #4030 doesn't need to happen again. We check that the worker file sizes stay within a given limit, and require people to explicitly up this limit if they decide to add new deps that grow the bundle size significantly. ### Change Type <!-- ❗ Please select a 'Type' label ❗️ --> - [ ] `feature` — New feature - [ ] `improvement` — Product improvement - [ ] `api` — API change - [ ] `bugfix` — Bug fix - [x] `other` — Changes that don't affect SDK users, e.g. internal or .com changes ### 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 - Add a brief release note for your PR here.
2024-06-27 13:48:17 +00:00
.bundle-meta.json
Reference in a new issue Copy permalink