Unify DID input with auto-detection of scope and name
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 36
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 7
Description
Description
Currently, the DID page uses separate input boxes for scope and name, which can be cumbersome when pasting full DIDs. This issue proposes implementing a single, unified input field that intelligently parses and auto-detects the scope and name components from pasted DIDs.
Current Behavior
- Two separate input fields for scope and name
- Left/right arrow keys switch between fields
- Users must manually split DIDs when pasting
Proposed Solution
- Single input box for DID entry
- Auto-detection logic to parse scope:name format
- Client-side validation with fallback to manual entry if parsing fails
- Remove left/right key navigation between fields
Implementation Details
- Implement parser for common DID formats (scope:name)
- Add client-side validation
- Show inline validation feedback
- Prompt for manual scope/name entry only when auto-detection fails
- Preserve backwards compatibility for direct scope/name entry
Acceptance Criteria
- Single input field replaces dual scope/name inputs
- Successfully parses and validates standard DID formats
- Provides clear feedback when validation fails
- Fallback mechanism for manual entry works correctly
- Left/right arrow keys no longer switch between fields
- Unit tests for DID parsing logic
Parent Issue
Part of #621 - [EPIC: Release 39] UX improvements
Parent Issue
- #621
Contributor guide
No contributing guide indexed for this repository
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 at the DID page and trace the existing scope/name inputs, arrow-key navigation, and current validation behavior. Add coverage for DID parsing and verify the unified field, inline errors, manual fallback, backward-compatible entry, and removal of arrow-key switching against the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100