DevTools UI improvement
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.3k
- Forks
- 214
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 18
Description
while developing modules for DevTools, It feels like some components are missing or some can be refactored to have more features. here is a list:
-
NTable: unavailable -
NPagination: unavailable -
NTabs: unavailable -
NDialogorNModal: we haveDialogcomponent in@nuxt/devtools, we can refactor and move it toui. -
NDrawer: we haveDrawerRight&DrawerBottomcomponent in@nuxt/devtools, we can refactor and move it toui. -
NNotification: we haveNotificationcomponent innuxt-devtools, we can refactor and move it toui. -
NNavbar: we haveNavbarcomponent in@nuxt/devtools, we can refactor and move it touibecause it's often use. -
NSplitPane: we havePanelLeftRightcomponent in@nuxt/devtools, we can refactor and move it toui. -
NTooltip: we are usingfloating-vuefor tooltips too in@nuxt/devtools, but I think we can add tooltip with only css -
NCommandPalette: we haveCommandPalettecomponent in@nuxt/devtools, we can refactor and move it toui -
NAlert: there is alreadyNTipbut I thinkNAlertis more common for use -
NBadge: we haveBadgecomponent in@nuxt/devtools, we can refactor and move it toui -
NLink&NTextExternalLink: can refactored to one component -
NButton&NIconButton: can refactored to one component (with support for group-buttons)
also there is this thought that maybe user wants to use @nuxt/devtools-ui for any other project so it would be neat if we add some other components too (e.g. NAvatar, NProgress ...)
If there are any additional components or improvements that have been overlooked, please feel free to add them to the list. let me know what you think, thanks
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 reviewing the existing components in @nuxt/devtools and the target @nuxt/devtools-ui package, focusing on the unchecked items in the list. Determine which components are actually required and whether the requested refactors share a settled design. Done means the scope is agreed and the selected components or refactors are implemented consistently in the UI package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, frontend, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100