2023-06-03 20:46:53 +00:00
|
|
|
import { BaseRecord, IdOf, RecordId } from '../BaseRecord'
|
2023-04-25 11:01:25 +00:00
|
|
|
import { createRecordType } from '../RecordType'
|
2023-06-27 12:25:55 +00:00
|
|
|
import { SerializedStore, Store } from '../Store'
|
2023-04-25 11:01:25 +00:00
|
|
|
import { StoreSchema } from '../StoreSchema'
|
|
|
|
|
2023-06-03 20:46:53 +00:00
|
|
|
interface Book extends BaseRecord<'book', RecordId<Book>> {
|
2023-04-25 11:01:25 +00:00
|
|
|
title: string
|
2023-05-24 11:25:41 +00:00
|
|
|
author: IdOf<Author>
|
2023-04-25 11:01:25 +00:00
|
|
|
numPages: number
|
|
|
|
}
|
|
|
|
|
|
|
|
const Book = createRecordType<Book>('book', {
|
|
|
|
validator: {
|
|
|
|
validate(value) {
|
|
|
|
const book = value as Book
|
|
|
|
if (!book.id.startsWith('book:')) throw Error()
|
|
|
|
if (book.typeName !== 'book') throw Error()
|
|
|
|
if (typeof book.title !== 'string') throw Error()
|
|
|
|
if (!Number.isFinite(book.numPages)) throw Error()
|
|
|
|
if (book.numPages < 0) throw Error()
|
|
|
|
return book
|
|
|
|
},
|
|
|
|
},
|
derived presence state (#1204)
This PR adds
- A new `TLInstancePresence` record type, to collect info about the
presence state in a particular instance of the editor. This will
eventually be used to sync presence data instead of sending
instance-only state across the wire.
- **Record Scopes**
`RecordType` now has a `scope` property which can be one of three
things:
- `document`: the record belongs to the document and should be synced
and persisted freely. Currently: `TLDocument`, `TLPage`, `TLShape`, and
`TLAsset`
- `instance`: the record belongs to a single instance of the store and
should not be synced at all. It should not be persisted directly in most
cases, but rather compiled into a kind of 'instance configuration' to
store alongside the local document data so that when reopening the
associated document it can remember some of the previous instance state.
Currently: `TLInstance`, `TLInstancePageState`, `TLCamera`, `TLUser`,
`TLUserDocument`, `TLUserPresence`
- `presence`: the record belongs to a single instance of the store and
should not be persisted, but may be synced using the special presence
sync protocol. Currently just `TLInstancePresence`
This sets us up for the following changes, which are gonna be pretty
high-impact in terms of integrating tldraw into existing systems:
- Removing `instanceId` as a config option. Each instance gets a
randomly generated ID.
- We'd replace it with an `instanceConfig` option that has stuff like
selectedIds, camera positions, and so on. Then it's up to library users
to get and reinstate the instance config at persistence boundaries.
- Removing `userId` as config option, and removing the `TLUser` type
altogether.
- We might need to revisit when doing auth-enabled features like locking
shapes, but I suspect that will be separate.
2023-04-27 18:03:19 +00:00
|
|
|
scope: 'document',
|
2023-04-25 11:01:25 +00:00
|
|
|
})
|
|
|
|
|
2023-06-03 20:46:53 +00:00
|
|
|
interface Author extends BaseRecord<'author', RecordId<Author>> {
|
2023-04-25 11:01:25 +00:00
|
|
|
name: string
|
|
|
|
isPseudonym: boolean
|
|
|
|
}
|
|
|
|
|
|
|
|
const Author = createRecordType<Author>('author', {
|
|
|
|
validator: {
|
|
|
|
validate(value) {
|
|
|
|
const author = value as Author
|
|
|
|
if (author.typeName !== 'author') throw Error()
|
|
|
|
if (!author.id.startsWith('author:')) throw Error()
|
|
|
|
if (typeof author.name !== 'string') throw Error()
|
|
|
|
if (typeof author.isPseudonym !== 'boolean') throw Error()
|
|
|
|
return author
|
|
|
|
},
|
|
|
|
},
|
derived presence state (#1204)
This PR adds
- A new `TLInstancePresence` record type, to collect info about the
presence state in a particular instance of the editor. This will
eventually be used to sync presence data instead of sending
instance-only state across the wire.
- **Record Scopes**
`RecordType` now has a `scope` property which can be one of three
things:
- `document`: the record belongs to the document and should be synced
and persisted freely. Currently: `TLDocument`, `TLPage`, `TLShape`, and
`TLAsset`
- `instance`: the record belongs to a single instance of the store and
should not be synced at all. It should not be persisted directly in most
cases, but rather compiled into a kind of 'instance configuration' to
store alongside the local document data so that when reopening the
associated document it can remember some of the previous instance state.
Currently: `TLInstance`, `TLInstancePageState`, `TLCamera`, `TLUser`,
`TLUserDocument`, `TLUserPresence`
- `presence`: the record belongs to a single instance of the store and
should not be persisted, but may be synced using the special presence
sync protocol. Currently just `TLInstancePresence`
This sets us up for the following changes, which are gonna be pretty
high-impact in terms of integrating tldraw into existing systems:
- Removing `instanceId` as a config option. Each instance gets a
randomly generated ID.
- We'd replace it with an `instanceConfig` option that has stuff like
selectedIds, camera positions, and so on. Then it's up to library users
to get and reinstate the instance config at persistence boundaries.
- Removing `userId` as config option, and removing the `TLUser` type
altogether.
- We might need to revisit when doing auth-enabled features like locking
shapes, but I suspect that will be separate.
2023-04-27 18:03:19 +00:00
|
|
|
scope: 'document',
|
2023-04-25 11:01:25 +00:00
|
|
|
}).withDefaultProperties(() => ({
|
|
|
|
isPseudonym: false,
|
|
|
|
}))
|
|
|
|
|
2024-04-16 11:13:54 +00:00
|
|
|
const schema = StoreSchema.create<Book | Author>({
|
|
|
|
book: Book,
|
|
|
|
author: Author,
|
|
|
|
})
|
2023-04-25 11:01:25 +00:00
|
|
|
|
|
|
|
describe('Store with validation', () => {
|
|
|
|
let store: Store<Book | Author>
|
|
|
|
|
|
|
|
beforeEach(() => {
|
|
|
|
store = new Store({ schema, props: {} })
|
|
|
|
})
|
|
|
|
|
|
|
|
it('Accepts valid records and rejects invalid records', () => {
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
store.put([Author.create({ name: 'J.R.R Tolkein', id: Author.createId('tolkein') })])
|
2023-04-25 11:01:25 +00:00
|
|
|
|
2023-11-13 11:51:22 +00:00
|
|
|
expect(store.query.records('author').get()).toEqual([
|
2023-04-25 11:01:25 +00:00
|
|
|
{ id: 'author:tolkein', typeName: 'author', name: 'J.R.R Tolkein', isPseudonym: false },
|
|
|
|
])
|
|
|
|
|
|
|
|
expect(() => {
|
|
|
|
store.put([
|
|
|
|
{
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
id: Book.createId('the-hobbit'),
|
2023-04-25 11:01:25 +00:00
|
|
|
typeName: 'book',
|
|
|
|
title: 'The Hobbit',
|
|
|
|
numPages: -1, // <---- Invalid!
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
author: Author.createId('tolkein'),
|
2023-04-25 11:01:25 +00:00
|
|
|
},
|
|
|
|
])
|
|
|
|
}).toThrow()
|
|
|
|
|
2023-11-13 11:51:22 +00:00
|
|
|
expect(store.query.records('book').get()).toEqual([])
|
2023-04-25 11:01:25 +00:00
|
|
|
})
|
|
|
|
})
|
|
|
|
|
|
|
|
describe('Validating initial data', () => {
|
2023-06-27 12:25:55 +00:00
|
|
|
let snapshot: SerializedStore<Book | Author>
|
2023-04-25 11:01:25 +00:00
|
|
|
|
|
|
|
beforeEach(() => {
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
const authorId = Author.createId('tolkein')
|
2023-04-25 11:01:25 +00:00
|
|
|
const authorRecord = Author.create({ name: 'J.R.R Tolkein', id: authorId })
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
const bookId = Book.createId('the-hobbit')
|
2023-04-25 11:01:25 +00:00
|
|
|
const bookRecord = Book.create({
|
|
|
|
title: 'The Hobbit',
|
|
|
|
numPages: 300,
|
|
|
|
author: authorId,
|
|
|
|
id: bookId,
|
|
|
|
})
|
|
|
|
|
|
|
|
snapshot = {
|
|
|
|
[authorId]: authorRecord,
|
|
|
|
[bookId]: bookRecord,
|
|
|
|
}
|
|
|
|
})
|
|
|
|
|
|
|
|
it('Validates initial data', () => {
|
|
|
|
expect(() => {
|
|
|
|
new Store<Book | Author>({ schema, initialData: snapshot, props: {} })
|
2024-02-04 11:19:47 +00:00
|
|
|
}).not.toThrow()
|
2023-04-25 11:01:25 +00:00
|
|
|
|
|
|
|
expect(() => {
|
|
|
|
// @ts-expect-error
|
|
|
|
snapshot[0].name = 4
|
|
|
|
|
|
|
|
new Store<Book | Author>({ schema, initialData: snapshot, props: {} })
|
2024-02-04 11:19:47 +00:00
|
|
|
}).toThrow()
|
2023-04-25 11:01:25 +00:00
|
|
|
})
|
|
|
|
})
|
|
|
|
|
|
|
|
describe('Create & update validations', () => {
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
const authorId = Author.createId('tolkein')
|
|
|
|
const bookId = Book.createId('the-hobbit')
|
2023-04-25 11:01:25 +00:00
|
|
|
const initialAuthor = Author.create({ name: 'J.R.R Tolkein', id: authorId })
|
|
|
|
const invalidBook = Book.create({
|
|
|
|
// @ts-expect-error - deliberately invalid data
|
|
|
|
title: 4,
|
|
|
|
numPages: 300,
|
|
|
|
author: authorId,
|
|
|
|
id: bookId,
|
|
|
|
})
|
|
|
|
const validBook = Book.create({
|
|
|
|
title: 'The Hobbit',
|
|
|
|
numPages: 300,
|
|
|
|
author: authorId,
|
|
|
|
id: bookId,
|
|
|
|
})
|
|
|
|
|
|
|
|
it('Prevents creating a store with invalid records', () => {
|
|
|
|
expect(
|
|
|
|
() =>
|
|
|
|
new Store<Book | Author>({
|
|
|
|
schema,
|
|
|
|
initialData: { [bookId]: invalidBook, [authorId]: initialAuthor },
|
|
|
|
props: {},
|
|
|
|
})
|
|
|
|
).toThrow()
|
|
|
|
})
|
|
|
|
|
|
|
|
it('Prevents updating invalid records to a store', () => {
|
|
|
|
const store = new Store<Book | Author>({
|
|
|
|
schema,
|
|
|
|
initialData: { [bookId]: validBook, [authorId]: initialAuthor },
|
|
|
|
props: {},
|
|
|
|
})
|
|
|
|
|
|
|
|
expect(() => {
|
|
|
|
store.put([invalidBook])
|
|
|
|
}).toThrow()
|
|
|
|
})
|
|
|
|
|
|
|
|
it('Prevents adding invalid records to a store', () => {
|
Independent instance state persistence (#1493)
This PR
- Removes UserDocumentRecordType
- moving isSnapMode to user preferences
- moving isGridMode and isPenMode to InstanceRecordType
- deleting the other properties which are no longer needed.
- Creates a separate pipeline for persisting instance state.
Previously the instance state records were stored alongside the document
state records, and in order to load the state for a particular instance
(in our case, a particular tab) you needed to pass the 'instanceId'
prop. This prop ended up totally pervading the public API and people ran
into all kinds of issues with it, e.g. using the same instance id in
multiple editor instances.
There was also an issue whereby it was hard for us to clean up old
instance state so the idb table ended up bloating over time.
This PR makes it so that rather than passing an instanceId, you load the
instance state yourself while creating the store. It provides tools to
make that easy.
- Undoes the assumption that we might have more than one instance's
state in the store.
- Like `document`, `instance` now has a singleton id
`instance:instance`.
- Page state ids and camera ids are no longer random, but rather derive
from the page they belong to. This is like having a foreign primary key
in SQL databases. It's something i'd love to support fully as part of
the RecordType/Store api.
Tests to do
- [x] Test Migrations
- [x] Test Store.listen filtering
- [x] Make type sets in Store public and readonly
- [x] Test RecordType.createId
- [x] Test Instance state snapshot loading/exporting
- [x] Manual test File I/O
- [x] Manual test Vscode extension with multiple tabs
- [x] Audit usages of store.query
- [x] Audit usages of changed types: InstanceRecordType, 'instance',
InstancePageStateRecordType, 'instance_page_state', 'user_document',
'camera', CameraRecordType, InstancePresenceRecordType,
'instance_presence'
- [x] Test user preferences
- [x] Manual test isSnapMode and isGridMode and isPenMode
- [ ] Test indexedDb functions
- [x] Add instanceId stuff back
### Change Type
- [x] `major` — Breaking Change
### Test Plan
1. Add a step-by-step description of how to test your PR here.
2.
- [ ] Unit Tests
- [ ] Webdriver tests
### Release Notes
- Add a brief release note for your PR here.
2023-06-05 14:11:07 +00:00
|
|
|
const newAuthorId = Author.createId('shearing')
|
2023-04-25 11:01:25 +00:00
|
|
|
const store = new Store<Book | Author>({
|
|
|
|
schema,
|
|
|
|
initialData: { [bookId]: validBook, [authorId]: initialAuthor },
|
|
|
|
props: {},
|
|
|
|
})
|
|
|
|
|
|
|
|
expect(() => {
|
|
|
|
store.put([
|
|
|
|
Author.create({
|
|
|
|
// @ts-expect-error - deliberately invalid data
|
|
|
|
name: 5,
|
|
|
|
id: newAuthorId,
|
|
|
|
}),
|
|
|
|
])
|
|
|
|
}).toThrow()
|
|
|
|
|
|
|
|
expect(store.get(newAuthorId)).toBeUndefined()
|
|
|
|
})
|
|
|
|
})
|