refactor: use UUID, remove redundant kiro tasks

[DaxServer]

No description provided.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Refactor

  • Standardized all unique identifiers across the schema editor to use UUIDs instead of strings.
  • Unified qualifier and snak data structures to a single, consistent format.
  • Removed outdated or redundant types and interfaces from the type system.
  • Updated all relevant components, stores, composables, and tests to reflect these type changes.

• Chores

  • Improved type safety and consistency throughout the frontend codebase.
  • Adjusted documentation and requirements to match the new identifier and qualifier conventions.

Walkthrough

This update replaces the QualifierSchemaMapping and ReferenceSnakSchemaMapping types with a unified PropertyValueMap type across the codebase, updates all relevant type annotations and function signatures, and enforces UUID typing for identifiers in schema-related interfaces. Documentation and test files are adjusted accordingly, and some acceptance criteria and tasks are revised or removed.

Changes

Cohort / File(s)	Change Summary
Spec Documentation Update .kiro/specs/wikibase-schema-editor/requirements.md, .kiro/specs/wikibase-schema-editor/tasks.md	Updated acceptance criteria and task references; removed certain tasks and criteria related to visual feedback and tooltips.
ESLint & TypeScript Config frontend/.eslintrc-auto-import.json, frontend/auto-imports.d.ts	Replaced QualifierSchemaMapping and ReferenceSnakSchemaMapping with PropertyValueMap in auto-imports and global type exports; added global UUID constant.
Type Definitions frontend/src/types/wikibase-schema.ts	Replaced string IDs with UUID types; removed QualifierSchemaMapping and ReferenceSnakSchemaMapping interfaces; introduced PropertyValueMap and updated all relevant usages.
Composables: Reference/Schema Builder frontend/src/composables/useReferenceValueMapping.ts, frontend/src/composables/useSchemaBuilder.ts	Updated function signatures and internal logic to use PropertyValueMap and UUID types; removed legacy types and updated ID generation to use crypto.randomUUID().
Store Logic frontend/src/stores/schema.store.ts	Updated function signatures and internal logic to use PropertyValueMap[] for qualifiers/references and UUID for statement IDs; adjusted imports and initial state values.
Component & Test Files (Qualifiers/References/Statements) frontend/src/components/ReferencesEditor.vue, frontend/src/components/QualifiersEditor.vue, frontend/src/components/StatementEditor.vue, frontend/src/components/StatementsEditor.vue, frontend/src/components/WikibaseSchemaEditor.vue, frontend/src/components/__tests__/*, frontend/src/composables/__tests__/*, frontend/src/stores/__tests__/*, frontend/src/types/__tests__/schema-mapping.test.ts	Replaced usages of removed types with PropertyValueMap; updated ID generation and test data to use UUIDs; adjusted imports and type annotations for consistency; updated event signatures and props to use UUIDs and unified qualifier/snaks types.
API Composable frontend/src/composables/useSchemaApi.ts	Updated function parameter types for schema and project IDs from string to UUID.
Build Configuration frontend/vite.config.ts	Added type-only auto-import for UUID from crypto in Vite AutoImport plugin configuration.

Sequence Diagram(s)

sequenceDiagram
    participant UI
    participant Store
    participant SchemaBuilder
    participant ReferenceMapping

    UI->>Store: addStatement(property, valueMapping, qualifiers: PropertyValueMap[], references: PropertyValueMap[])
    Store->>SchemaBuilder: buildStatement(property, valueMapping, ..., qualifiers, references)
    SchemaBuilder->>Store: StatementSchemaMapping (with UUID id, qualifiers: PropertyValueMap[], references: PropertyValueMap[])
    Store-->>UI: UUID (statement id)
    
    UI->>ReferenceMapping: createCitationReference(snaks: PropertyValueMap[])
    ReferenceMapping-->>UI: ReferenceSchemaMapping (with UUID id, snaks: PropertyValueMap[])

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15–25 minutes

Possibly related PRs

• feat(wikibase-schema-editor): build reference value mapping #100: The main PR refactors and unifies qualifier and reference snak types to PropertyValueMap and standardizes identifier types to UUID across the Wikibase schema editor, while the retrieved PR introduces the initial implementation of the useReferenceValueMapping composable and related reference snak handling, including new types and UI support for managing reference snaks; thus, the main PR builds upon and modifies the structures and types introduced in the retrieved PR, indicating a direct and strong code-level relationship.
• feat(wikibase-schema-editor): create statement editor with value mappings #91: The main PR focuses on refactoring and type unification around UUID usage and replacing qualifier and reference snak types with a unified PropertyValueMap type across the wikibase-schema-editor codebase, while the retrieved PR introduces the initial creation of the StatementEditor component with value mapping functionality; thus, the main PR builds upon and modifies the types and interfaces used in the StatementEditor introduced by the retrieved PR, indicating a direct and strong connection at the code level.
• docs: add kiro tasks for Wikibase Schema Editor spec #65: Adds a comprehensive implementation plan for the Wikibase Schema Editor, which is related to the acceptance criteria and task updates in this PR.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 d81f565 and 5b809c5.

📒 Files selected for processing (1)

• frontend/src/components/WikibaseSchemaEditor.vue (9 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/src/components/WikibaseSchemaEditor.vue

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore

---

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 generate unit tests to generate unit tests for 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.