mirror of
https://github.com/ankitects/anki.git
synced 2025-09-18 14:02:21 -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.
69 lines
1.5 KiB
TypeScript
69 lines
1.5 KiB
TypeScript
// Copyright: Ankitects Pty Ltd and contributors
|
|
// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html
|
|
|
|
import { nodeIsElement } from "@tslib/dom";
|
|
|
|
export type Matcher = (element: Element) => boolean;
|
|
|
|
function findParent(current: Node, base: Element): Element | null {
|
|
if (current === base) {
|
|
return null;
|
|
}
|
|
|
|
return current.parentElement;
|
|
}
|
|
|
|
/**
|
|
* Similar to element.closest(), but allows you to pass in a predicate
|
|
* function, instead of a selector
|
|
*
|
|
* @remarks
|
|
* Unlike element.closest, this will not match against `node`, but will start
|
|
* at `node.parentElement`.
|
|
*/
|
|
export function findClosest(
|
|
node: Node,
|
|
base: Element,
|
|
matcher: Matcher,
|
|
): Element | null {
|
|
if (nodeIsElement(node) && matcher(node)) {
|
|
return node;
|
|
}
|
|
|
|
let current = findParent(node, base);
|
|
|
|
while (current) {
|
|
if (matcher(current)) {
|
|
return current;
|
|
}
|
|
|
|
current = findParent(current, base);
|
|
}
|
|
|
|
return null;
|
|
}
|
|
|
|
/**
|
|
* Similar to `findClosest`, but will go as far as possible.
|
|
*/
|
|
export function findFarthest(
|
|
node: Node,
|
|
base: Element,
|
|
matcher: Matcher,
|
|
): Element | null {
|
|
let farthest: Element | null = null;
|
|
let current: Node | null = node;
|
|
|
|
while (current) {
|
|
const next = findClosest(current, base, matcher);
|
|
|
|
if (next) {
|
|
farthest = next;
|
|
current = findParent(next, base);
|
|
} else {
|
|
break;
|
|
}
|
|
}
|
|
|
|
return farthest;
|
|
}
|