Anders Semb Hermansen 4278e724f5 fix(next): richtext field is read-only for expired lock (#13789) ...

### What?

Opening a document with an expired lock and richtext caused the richtext
to be read-only.

### Why?

The changes in #13579 made the richtext read only if isLocked is set.
But the server side implementation of isLocked did not consider expired
locks.

### How?

Update the server-side getIsLocked to also consider expired locks by not
loading them.

2025-09-12 07:46:51 -07:00

..

collections

fix(next): richtext fields not read-only for locked documents (#13579)

2025-08-25 08:44:01 -07:00

globals

fix(next, ui): exclude expired locks for globals (#8914)

2024-10-28 21:49:50 -04:00

.gitignore

feat: lock documents while being edited (#7970)

2024-09-17 14:04:48 -04:00

config.ts

feat: query presets (#11330)

2025-03-24 13:16:39 -04:00

e2e.spec.ts

fix(next): richtext field is read-only for expired lock (#13789)

2025-09-12 07:46:51 -07:00

int.spec.ts

docs: improve jobs autorun docs, adds e2e test (#12196)

2025-06-05 09:19:19 -07:00

payload-types.ts

fix(next): richtext fields not read-only for locked documents (#13579)

2025-08-25 08:44:01 -07:00

schema.graphql

feat: lock documents while being edited (#7970)

2024-09-17 14:04:48 -04:00

seed.ts

chore: fix various e2e test setup issues (#12670)

2025-06-04 17:34:37 -03:00

slugs.ts

feat: query presets (#11330)

2025-03-24 13:16:39 -04:00

tsconfig.eslint.json

feat: lock documents while being edited (#7970)

2024-09-17 14:04:48 -04:00

tsconfig.json

feat: lock documents while being edited (#7970)

2024-09-17 14:04:48 -04:00