edc5dae103
Clearing a page's body in git advanced the vault ref past the empty commit, but the persistence store-side empty-guard rejected the empty write (reloading the non-empty DB content) — so Docmost kept the old body while the vault held the empty one, a permanent silent vault<->Docmost divergence that never re-detects. A git-sync write is authoritative and its content IS the vault file, so an empty incoming doc there is a DELIBERATE clear (no transient-glitch empties for a file-sourced write). Allow it (lastUpdatedSource==='git-sync'), mirroring the #251 intentional-clear allowance for the user-signalled source. Verified on stand: a git-side body clear takes the page body 28 -> 0 (page not trashed); previously it stayed 28 (diverged). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A progressive Node.js framework for building efficient and scalable server-side applications.
Description
Nest framework TypeScript starter repository.
Installation
$ npm install
Running the app
# development
$ npm run start
# watch mode
$ npm run start:dev
# production mode
$ npm run start:prod
Migrations
# This creates a new empty migration file named 'init'
$ npm run migration:create --name=init
# Generates 'init' migration file from existing entities to update the database schema
$ npm run migration:generate --name=init
# Runs all pending migrations to update the database schema
$ npm run migration:run
# Reverts the last executed migration
$ npm run migration:revert
# Reverts all migrations
$ npm run migration:revert
# Shows the list of executed and pending migrations
$ npm run migration:show
## Test
```bash
# unit tests
$ npm run test
# e2e tests
$ npm run test:e2e
# test coverage
$ npm run test:cov
Support
Nest is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please read more here.
Stay in touch
- Author - Kamil Myśliwiec
- Website - https://nestjs.com
- Twitter - @nestframework
License
Nest is MIT licensed.