ecrin-github / ecrin-github/rms-portal-new
usage of internal ids in the UI
Open
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
we should avoid the use of internal ids in the UI, since they are not very informative to identify the object.
check if we need to add a field.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the UI components that display internal IDs and trace the corresponding object data through the frontend and backend. Check whether an informative field already exists before deciding whether the data model needs another field. Done means the UI identifies objects without exposing internal IDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100