Implement use case for settings in dataset page

Open
#212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api

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.

Description

GREI Re-arch Original size: 3 Size: 3 SPA: Dataset View Page

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.
Dominant language
TypeScript
Stars
20
Forks
11
Avg merge
2d 5h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IQSS/dataverse-client-javascript

All issues in IQSS/dataverse-client-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.