Files

claude code agent 227 3ebe24bee2 feat(footnotes): multi-backlinks — definition returns to ALL its references (#168 )

After #166 a repeated `[^a]` is one footnote (reuse): one number, one
definition, N forward links. But the definition's ↩ only returned to the
FIRST reference. Now a definition with N references shows ↩ a b c …, each
backlink scrolling to its own occurrence (Pandoc/Wikipedia convention); a
single-reference footnote keeps the plain ↩ unchanged.

- editor-ext: `computeFootnoteRefCounts(doc)` (id -> occurrence count) cached
  alongside the number map in the numbering plugin state; `getFootnoteRefCount`
  getter (O(1), no per-render doc walk). `scrollToReference(id, index?)` picks
  the index-th `sup[data-footnote-ref][data-id]` occurrence (document order),
  falling back to the first.
- client: FootnoteDefinitionView renders one lettered link (a, b, c, … aa …)
  per occurrence when refCount > 1; the chrome stays after the contentDOM so
  the #146 caret invariant holds. i18n keys (ru) added.

Tests: computeFootnoteRefCounts + getFootnoteRefCount (reuse counts, unknown
id => 0); structure test gains 3 cases (N lettered links render, click jumps
to the n-th occorrence, single ref => one ↩). NOTE: the visual layout of the
backlink row needs a real browser to verify (jsdom can't); the structural and
behavioral contract is covered headless.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-25 05:17:56 +03:00

public

feat(footnotes): multi-backlinks — definition returns to ALL its references (#168 )

2026-06-25 05:17:56 +03:00

scripts

fix(dictation): also ship the plain onnxruntime-web wasm variant

2026-06-22 17:40:45 +03:00

src

feat(footnotes): multi-backlinks — definition returns to ALL its references (#168 )

2026-06-25 05:17:56 +03:00

.dockerignore

fixes

2024-06-07 17:29:34 +01:00

.gitignore

…

eslint.config.mjs

chore: fix linting (#544 )

2024-12-09 14:51:31 +00:00

index.html

feat(brand): roll out Gitmost logo, favicon and app name

2026-06-18 00:12:26 +03:00

package.json

fix(dictation): self-host Silero VAD / onnxruntime-web assets

2026-06-22 17:19:11 +03:00

postcss.config.js

…

README.md

…

tsconfig.json

…

tsconfig.node.json

…

vite.config.ts

feat(client): show git-describe version next to the brand logo

2026-06-18 04:51:21 +03:00

vitest.config.ts

test(refactor-tail): extract pure cores + cover collab/share/ai-chat/client gate

2026-06-21 19:10:27 +03:00

vitest.setup.ts

chore(comments): address PR #143 review (operator doc, badge test, dedup, type)

2026-06-23 23:56:26 +03:00

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

Configure the top-level parserOptions property like this:

   parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json'],
    tsconfigRootDir: __dirname,
   },

Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
Optionally add plugin:@typescript-eslint/stylistic-type-checked
Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list