athityakumar / athityakumar/harvey
A better case mapping
- Dominant language
- HTML
- Stars
- 10
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Instead of having different `CASE_ID_TO_NAME` and `CASE_NAME_TO_ID` mappings, just have a `CASE_MAPPING` that looks like this:
```js
CASE_MAPPING = [
{
id: IO....,
title: ...,
subject_ids: [],
keyword_ids: []
},
{
id: IO....,
title: ...,
subject_ids: [],
keyword_ids: []
}
]
KEYWORDS = {keyword_id: keyword_title}
SUBJECTS = {subject_id: subject_title}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the existing CASE_ID_TO_NAME and CASE_NAME_TO_ID mappings, then inspect the code that reads or updates them. Replace the duplicated mapping structure with the proposed CASE_MAPPING, KEYWORDS, and SUBJECTS structures, and verify that all existing case, keyword, and subject lookups still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100