terraphim / terraphim/terraphim-ai
[Phase 4.1] Migrate Simple Svelte Components
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 62
- Forks
- 5
- Avg merge
- 2h 27m
- Merged PRs (30d)
- 1
Description
Overview
Migrate remaining simple leaf Svelte components to Web Components.
Agent Workflow
Step 1: Architecture (@zestic-frontend-architect)
Identify simple leaf components (BackButton, Shortcuts, ResultItem, etc.), design migration strategy, specify API compatibility layer, create migration blueprint for each.
Step 2: Implementation (@zestic-front-craftsman)
Migrate each component per blueprint, maintain API compatibility, write migration tests, document migration guide.
Components to Migrate
- BackButton → terraphim-back-button
- Shortcuts → terraphim-shortcuts
- ResultItem → terraphim-result-item
- KGContextItem → terraphim-kg-context-item
- SessionList → terraphim-session-list
- Modals (ArticleModal, AtomicSaveModal, KGSearchModal, ContextEditModal)
Related Issues
Epic: #230, Dependencies: #231, #232
Labels
web-components, phase-4, migration, architecture, implementation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Epic #230 and dependencies #231 and #232, then identify the listed leaf components: BackButton, Shortcuts, ResultItem, KGContextItem, SessionList, and the four modals. Done means each component is migrated with API compatibility, migration tests are added, and the migration guide is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100