Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Filter the Analysis Catalog by lexicon link

オープン
  • 何か問題がありますか？
#564 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
38/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
frontend, testing

調査の方向性

Start with src/utils/analysis-query.ts and its analysis-query.test.ts tests, then inspect the catalog panel’s existing filter controls and reconcileFilters. First resolve the listed design choices: what counts as linked, when to show the filter, whether refs need to match the active lexicon, and whether to use one or two toggles. Done means the chosen behavior is available in the panel and covered for each choice, including rows without morphemes and morphemes with an empty form; the issue also depends on #540.

索引モデルが issue の本文から書いたものです。

説明

Part of #46. #228 lists it as a likely follow-up and leaves it out of its own scope.

Lets a user narrow the Analysis Catalog to rows that are, or aren't, linked to a lexicon sense. For example, they can find what still needs linking, or check what an import brought in.

Scope

  • A filter on CatalogFilters, applied in passesFilters (src/utils/analysis-query.ts) alongside the existing toggle filters, and added to TOGGLE_FILTER_KEYS if it is a toggle.
  • A control for it in the catalog panel, next to the other filters.
  • Tests in analysis-query.test.ts for each choice, including rows with no morphemes and morphemes with an empty form.

To decide

  1. What counts as linked.
    • The token's glossSenseRef only: simple, and matches what the row header shows first. It misses rows linked only at the morpheme level.
    • Any morpheme's senseRef: finds morpheme-level work. It misses whole-word and idiom links, and a token with no morphemes can never match it.
    • Either level: a single meaning of "linked". But "unlinked" then means "no ref anywhere", so a partly linked breakdown counts as linked.
    • Separate filters per level: precise, but adds two controls where the others add one.
    • "Fully linked": the token plus every morpheme with a non-empty form. It matches what "done" means, but it's harder to explain and test.
  2. When the filter is offered.
    • Only while a lexicon is linked: matches the original ask. But #228 and #540 show a ref an analysis carries even in tier 0 or when the provider can't search, so a tier-0 user with imported refs could see links but not filter by them. reconcileFilters would also have to drop an active selection when the lexicon is unlinked, the same way it drops a withdrawn facet.
    • Always: consistent with how refs are displayed, and needs no lexicon state in the query. In tier 0 with no refs at all, though, it's a control that always returns everything or nothing.
    • Whenever any row carries a ref: offered when it can matter, with no lexicon state needed. It is derived like a facet, so the control can disappear while it is active, which reconcileFilters has to handle.
  3. Ref presence or resolution.
    • Presence: pure and synchronous like every other catalog filter, with no lexicon calls. A dangling ref (entry deleted, provider offline) still counts as linked.
    • Resolvable refs: "linked" means something the user can open. But this needs every row resolved, which conflicts with resolving only on-screen rows (#227, #540), and results change when the provider goes offline.
  4. Refs from another provider (#225).
    • Any ref counts: no knowledge of the active lexicon needed.
    • Only refs matching the active lexicon's authority and project: matches what the user can act on. The query then depends on which lexicon is active, and a row linked to an old lexicon counts as unlinked.
  5. Shape.
    • One tri-state toggle, like morphemes: 'has' | 'lacks'. It matches the existing pattern, but only fits if question 1 lands on a single level.
    • Two independent toggles: this suits per-level filtering, though it uses more panel space.

Not here

  • Filtering by disagreement between the typed gloss and the resolved sense gloss. It needs every row resolved (see question 3).
  • Filtering by linked entry or sense, which is a value facet and would need resolution.
  • Linking and unlinking: #542.

Depends on

  • #540, so a kept row shows why it was kept.

Notes

Nothing here writes, so it doesn't wait for the data layer plan (#417). getCatalogRows in #456 takes the same CatalogFilters; whichever lands second carries the filter.

主要言語
TypeScript
スター
2
フォーク
0
平均マージ
1日 9時間
マージ済み PR（30日）
78

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

sillsdev/interlinearizer-extension のほかの issue

sillsdev/interlinearizer-extension の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。