mirror of
https://github.com/ankitects/anki.git
synced 2025-09-19 14:32:22 -04:00

* Update to latest Node LTS * Add sveltekit * Split tslib into separate @generated and @tslib components SvelteKit's path aliases don't support multiple locations, so our old approach of using @tslib to refer to both ts/lib and out/ts/lib will no longer work. Instead, all generated sources and their includes are placed in a separate out/ts/generated folder, and imported via @generated instead. This also allows us to generate .ts files, instead of needing to output separate .d.ts and .js files. * Switch package.json to module type * Avoid usage of baseUrl Incompatible with SvelteKit * Move sass into ts; use relative links SvelteKit's default sass support doesn't allow overriding loadPaths * jest->vitest, graphs example working with yarn dev * most pages working in dev mode * Some fixes after rebasing * Fix/silence some svelte-check errors * Get image-occlusion working with Fabric types * Post-rebase lock changes * Editor is now checked * SvelteKit build integrated into ninja * Use the new SvelteKit entrypoint for pages like congrats/deck options/etc * Run eslint once for ts/**; fix some tests * Fix a bunch of issues introduced when rebasing over latest main * Run eslint fix * Fix remaining eslint+pylint issues; tests now all pass * Fix some issues with a clean build * Latest bufbuild no longer requires @__PURE__ hack * Add a few missed dependencies * Add yarn.bat to fix Windows build * Fix pages failing to show when ANKI_API_PORT not defined * Fix svelte-check and vitest on Windows * Set node path in ./yarn * Move svelte-kit output to ts/.svelte-kit Sadly, I couldn't figure out a way to store it in out/ if out/ is a symlink, as it breaks module resolution when SvelteKit is run. * Allow HMR inside Anki * Skip SvelteKit build when HMR is defined * Fix some post-rebase issues I should have done a normal merge instead.
52 lines
1.6 KiB
Svelte
52 lines
1.6 KiB
Svelte
<!--
|
|
Copyright: Ankitects Pty Ltd and contributors
|
|
License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html
|
|
-->
|
|
<script lang="ts">
|
|
import type { GraphsResponse } from "@generated/anki/stats_pb";
|
|
import {
|
|
getGraphPreferences,
|
|
graphs,
|
|
setGraphPreferences,
|
|
} from "@generated/backend";
|
|
import type { Writable } from "svelte/store";
|
|
|
|
import { autoSavingPrefs } from "$lib/sveltelib/preferences";
|
|
|
|
import { daysToRevlogRange } from "./graph-helpers";
|
|
|
|
export let search: Writable<string>;
|
|
export let days: Writable<number>;
|
|
|
|
const prefsPromise = autoSavingPrefs(
|
|
() => getGraphPreferences({}),
|
|
setGraphPreferences,
|
|
);
|
|
|
|
let sourceData = null as null | GraphsResponse;
|
|
let loading = true;
|
|
$: updateSourceData($search, $days);
|
|
|
|
async function updateSourceData(search: string, days: number): Promise<void> {
|
|
// ensure the fast-loading preferences come first
|
|
await prefsPromise;
|
|
loading = true;
|
|
try {
|
|
sourceData = await graphs({ search, days });
|
|
} finally {
|
|
loading = false;
|
|
}
|
|
}
|
|
|
|
$: revlogRange = daysToRevlogRange($days);
|
|
</script>
|
|
|
|
<!--
|
|
We block graphs loading until the preferences have been fetched, so graphs
|
|
don't have to worry about a null initial value. We don't do the same for the
|
|
graph data, as it gets updated as the user changes options, and we don't want
|
|
the current graphs to disappear until the new graphs have finished loading.
|
|
-->
|
|
{#await prefsPromise then prefs}
|
|
<slot {revlogRange} {prefs} {sourceData} {loading} />
|
|
{/await}
|