Relation Type menu options text in the Related Publication not displaying properly; no spaces between words
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in the Related Publication section of the dataset metadata UI and reproduce the issue with a Relation Type dropdown option while editing and viewing a dataset. Trace how the option labels are rendered, compare the Modern UI with the JSA display, and verify that every Relation Type phrase includes spaces in both contexts.
Written by the indexing model from the issue text.
Description
What steps does it take to reproduce the issue?
-
When does this issue occur?
When editing and viewing metadata on a dataset where the Related Publication field uses an option from the Relation Type dropdown menu. -
Which page(s) does it occur on?
I noticed it on this dataset page: https://dataverse.harvard.edu/modern/datasets?persistentId=doi:10.7910/DVN/IKIVID -
What happens?
-
To whom does it occur (all users, curators, superusers)?
Superuser and not logged in at all. Didn't test other login types. -
What did you expect to happen?
I expect the phrases in the Relation Type dropdown menu have a space between each word.
Which version of Dataverse Frontend are you using?
v. 6.10.1 build iqss-4|frontend version: 371cf9773
Any related open or closed issues to this bug report?
Screenshots:
How the same text is displayed in the JSA version:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
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.
More from IQSS/dataverse-frontend
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
IQSS/dataverse-frontend#1001 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
IQSS/dataverse-frontend#1073 · 1 comment ·
-
Size: 30 SPA
Difficulty 4/5 3-5 days Newbie friendliness 38/100
IQSS/dataverse-frontend#1069 ·
-
Size: 30 SPA
IQSS/dataverse-frontend#1064 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
IQSS/dataverse-frontend#1063 ·
All issues in IQSS/dataverse-frontend
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100