Extract a typed repository interface (adapters/repo.ts) from the scattered store/view -> api.* calls, backed by adapters/rest.ts (verbatim HTTP mapping) and selected through adapters/index.ts. Every store and the notes-facing views now depend on `repo`, never the HTTP client directly -- the seam the offline local source (M10.5, over Tauri invoke) plugs into next. Behavior-preserving for web: rest.ts maps each semantic method to the exact endpoint the code called before; query-string and multipart building moved out of the stores/views into rest.ts (the one place that knows the URL shape). Client-side logic (reconcile/sort/optimistic reorder/toasts) stays in the stores. GraphView + admin SettingsView keep direct api calls -- out of the offline-core scope (M10.5 is board/editor/capture/search/filter/labels/ checklists/reminders). Task 1992. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FRgehjoz7Yv8LkUfADxACm
33 lines
848 B
TypeScript
33 lines
848 B
TypeScript
import { defineStore } from "pinia";
|
|
import { ref } from "vue";
|
|
import { repo } from "../adapters";
|
|
|
|
export interface TitleEntry {
|
|
id: string;
|
|
title: string;
|
|
}
|
|
|
|
// Owner's {id,title} index, used to resolve [[wiki-links]] client-side.
|
|
export const useTitlesStore = defineStore("titles", () => {
|
|
const items = ref<TitleEntry[]>([]);
|
|
const loaded = ref(false);
|
|
|
|
async function load(): Promise<void> {
|
|
if (loaded.value) return;
|
|
items.value = await repo.notes.titles();
|
|
loaded.value = true;
|
|
}
|
|
|
|
async function reload(): Promise<void> {
|
|
loaded.value = false;
|
|
await load();
|
|
}
|
|
|
|
function resolve(title: string): TitleEntry | null {
|
|
const norm = title.trim().toLowerCase();
|
|
return items.value.find((t) => t.title.trim().toLowerCase() === norm) ?? null;
|
|
}
|
|
|
|
return { items, loaded, load, reload, resolve };
|
|
});
|