IQSS / IQSS/dataverse-client-javascript
Implement use case for settings in dataset page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 11
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 1
Description
A TODO existing describes that the SettingJSDataverseRepository in front end repo currently has a getByName method that returns a mocked response, and this method should be implemented to fetch actual setting name. There is no use case related to settings now, so a use case and integration may in demand.
- Another Todo is also related to settings.
Contributor guide
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 with src/settings/infrastructure/SettingJSDataverseRepository.ts and the linked TODO in the frontend, then review src/sections/dataset/dataset-files/files-table/file-actions/edit-files-menu/EditFilesOptions.tsx for the related integration point. Done means the settings use case exists, getByName fetches the actual setting, and the dataset page uses it instead of a mocked response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100