feat(wikibase-schema-editor): create basic isolated schema store

[DaxServer]

Addresses Task 4 of #66

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Introduced a new schema management system for Wikibase mappings, enabling users to create, edit, and manage schema details directly in the application.
  • Added support for managing item terms (labels, descriptions, aliases) and statements with property references and value mappings.
  • Implemented state tracking features, including dirty state indicators and last saved timestamps.

• Tests

  • Added comprehensive tests to ensure correct behavior and reactivity of the schema management features.

• Chores

  • Updated auto-import configurations to enable seamless usage of the new schema store throughout the frontend.

Walkthrough

A new Pinia store for managing Wikibase schema mappings was implemented in the frontend, along with a comprehensive test suite for its behavior. Auto-import declarations and ESLint configuration were updated to recognize the new store. Additionally, the project task list was updated to mark relevant tasks as completed.

Changes

File(s)	Change Summary
.kiro/specs/wikibase-schema-editor/tasks.md	Updated task list: marked "Build validation error handling system" and "Create basic schema store with TDD" as completed.
frontend/.eslintrc-auto-import.json frontend/auto-imports.d.ts	Added useSchemaStore to global auto-imports and ESLint config for recognition and type inference.
frontend/src/stores/schema.store.ts	Introduced new Pinia store useSchemaStore for Wikibase schema mapping state and actions.
frontend/src/stores/tests/schema.store.test.ts	Added comprehensive test suite for the useSchemaStore Pinia store, verifying state, actions, and reactivity.

Sequence Diagram(s)

sequenceDiagram
    participant Component
    participant useSchemaStore (Pinia)
    participant WikibaseSchemaMapping (State)

    Component->>useSchemaStore: Access computed properties (e.g., itemTerms, statements)
    Component->>useSchemaStore: Call actions (e.g., createSchema, addLabelMapping)
    useSchemaStore->>WikibaseSchemaMapping: Update state (e.g., add label, add statement)
    useSchemaStore-->>Component: Reactively update computed properties and state

Loading

Possibly related PRs

• docs: add kiro tasks for Wikibase Schema Editor spec #65: Adds the initial task list for the Wikibase Schema Editor, modifying the same tasks.md file as this PR but at an earlier stage.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 41b4924 and 4b9d6ca.

📒 Files selected for processing (5)

• .kiro/specs/wikibase-schema-editor/tasks.md (1 hunks)
• frontend/.eslintrc-auto-import.json (1 hunks)
• frontend/auto-imports.d.ts (2 hunks)
• frontend/src/stores/__tests__/schema.store.test.ts (1 hunks)
• frontend/src/stores/schema.store.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

**/*.{js,ts,jsx,tsx}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

• .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc

**/*.{html,ts,css}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

• .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc

**/*.{html,js,ts,jsx,tsx}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

• .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc

🔇 Additional comments (21)

frontend/.eslintrc-auto-import.json (1)

315-315: LGTM! Auto-import configuration properly updated.

The addition of useSchemaStore to the globals configuration correctly enables auto-import functionality for the new Pinia store, following the established pattern in the codebase.

.kiro/specs/wikibase-schema-editor/tasks.md (2)

15-15: Task completion correctly tracked.

The validation error handling system implementation is appropriately marked as completed, aligning with the comprehensive schema store implementation.

---

21-21: Schema store with TDD implementation completed.

The task completion accurately reflects the comprehensive implementation of the basic schema store with thorough test coverage, following TDD principles.

frontend/auto-imports.d.ts (2)

262-262: TypeScript declaration correctly added.

The global constant declaration for useSchemaStore properly enables auto-import with type inference, following the established pattern in the codebase.

---

614-614: Vue component properties correctly extended.

The readonly property addition to ComponentCustomProperties interface enables proper type support for the store in Vue components, maintaining consistency with other store declarations.

frontend/src/stores/__tests__/schema.store.test.ts (8)

1-9: Excellent test imports and setup.

The test imports correctly use bun:test framework as specified in the coding guidelines, and proper TypeScript types are imported for comprehensive type safety.

---

13-16: Proper test setup with Pinia store initialization.

The beforeEach setup correctly initializes a fresh Pinia instance for each test, ensuring test isolation and preventing state leakage between tests.

---

18-36: Comprehensive initialization testing.

The tests thoroughly verify both the initial state and computed properties, ensuring the store starts in a clean, predictable state.

---

38-89: Excellent auto-creation behavior testing.

The tests comprehensively verify the auto-creation logic, including proper default values, structure validation, and ensuring existing schemas aren't overwritten. This is crucial functionality that's well-tested.

---

91-147: Thorough schema creation and initialization testing.

The tests cover all aspects of schema creation including unique ID generation, proper structure initialization, and setting existing schemas with correct state management.

---

149-334: Comprehensive CRUD operations testing.

The tests thoroughly verify all mapping operations (labels, descriptions, aliases) and statement management, including edge cases like multiple aliases per language and proper state updates.

---

336-374: Excellent persistence state testing.

The tests properly verify the persistence tracking functionality, including marking as saved, clearing state, and loading state management.

---

376-450: Outstanding reactivity testing.

The tests comprehensively verify that computed properties react correctly to state changes, which is crucial for Vue.js applications and ensures proper UI updates.

frontend/src/stores/schema.store.ts (8)

1-18: Excellent imports and state initialization.

The imports correctly use Pinia composition API and proper TypeScript types. The state initialization with ref() for reactive values follows Vue.js best practices.

---

20-48: Innovative auto-creation pattern in computed property.

The currentSchema computed property with auto-creation logic is an elegant solution that ensures a schema always exists when needed. The use of Bun.randomUUIDv7() follows the coding guidelines, and the default schema structure is comprehensive.

---

50-68: Well-designed computed properties with safe accessors.

The computed properties provide safe access to schema data with proper fallbacks, ensuring the store remains reactive while preventing null reference errors.

---

70-103: Comprehensive schema management actions.

The createSchema and setSchema actions properly handle schema lifecycle with consistent timestamp management and state tracking. The updateSchemaName action demonstrates proper use of the auto-creation pattern.

---

105-157: Robust terms mapping management.

The mapping actions for labels, descriptions, and aliases are well-implemented with proper array handling for aliases and cleanup logic. The consistent use of markDirty() ensures state tracking works correctly.

---

159-197: Excellent statement management functionality.

The statement operations are comprehensive, including proper ID generation, rank management, and array manipulation. The return of statement ID from addStatement enables proper reference tracking.

---

199-224: Proper persistence and utility functions.

The persistence tracking with markAsSaved, state clearing, and the helper markDirty function all follow good practices for state management and provide necessary functionality for the store lifecycle.

---

226-257: Excellent store API with proper encapsulation.

The return statement properly exposes readonly state variables, all computed properties, and actions, providing a clean API while protecting internal state from external mutation.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.