mirror of
https://github.com/zadam/trilium.git
synced 2026-09-12 11:40:19 +05:00
d595fb33e8
CoreApiTester now seeds the execution context from the trilium-* request headers, so Pattern 0 documents how to drive a hoisted request and warns that a spec omitting trilium-hoisted-note-id exercises the unhoisted path. Anything reading hoistedNoteService.getHoistedNoteId() — quick search, autocomplete, SearchContext's implicit ancestorNoteId — sees "root" without it, so a passing spec is not evidence that scoping works. A contributor's quick-search PR asserted exactly that and proved nothing. The Windows note covered only `pnpm --filter … exec vitest`; the auto-install fires for a package's own test script too. It now names the symptom seen here: EPERM / Access is denied on a node_modules directory VS Code holds open, which rolls back cleanly but loses the run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| adding-internal-api-route | ||
| adding-llm-mcp-tools | ||
| analyzing-backend-bundle | ||
| analyzing-coverage | ||
| building-client-ui | ||
| ckeditor5-plugin-development | ||
| ckeditor5-reviewing | ||
| ckeditor5-testing | ||
| cutting-a-release | ||
| developing-capacitor-mobile | ||
| developing-electron-desktop | ||
| developing-standalone | ||
| evolving-the-data-model | ||
| measure-startup-requests | ||
| packaging-for-flathub | ||
| profiling-client-performance | ||
| translating-locales | ||
| working-with-translations | ||
| writing-unit-tests | ||