[Research structure] Concepts are not always 1:1 between libraries and research pages
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
I'm working on a Popup research page, and found that the "Dropdown" from Carbon has a base concept that applies to multiple "concepts" on the Popup research page. Right now I have to add like this:
"concepts": [
{
"name": "dropdown",
"openUIName": "content picker",
...
},
{
"name": "dropdown",
"openUIName": "menu",
...
},
]
which is sort of wasteful, re-declaring all the information in order to route this into both the content picker and menu concepts on the Popup research page. openUIName should be able to take an array of concepts.
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 by inspecting the Popup research page and the concepts structure shown in the issue, then trace how openUIName is consumed for routing. Done means one base concept can target multiple research-page concepts without repeating its other information, with existing concept data remaining compatible.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100