You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📝 (Improvement/Breaking) Icon component: dynamic icons instead of only baked in ones --> needs research, check other design systems (medium/complex) Prio 1
possible solution 1: rewrite Icon component to accept svg as prop
Remove css duplication in global.css and theme.css (the CSS variables and global styles are duplicated, one is used for ui component styles and the other is exported to be used as theme basis in apps). It should be possible to extract the common pieces into a separate css file that both import to remove the duplication
(Improvement) Badge component should nicely display single-digit or low digit numbers. Maybe needs a new component --> research
Upload Dialog (no new component yet, UX pattern only for now)
(Feature) ComboBox: Discuss and decide whether we want to introduce a generically useable mechanism to allow developers to clear ComboBox immediately after changing/ selecting a value, as is needed in filters with immediate effect where we want users to be able to select another filter suing the same ComboBox. ([Feature](ComboBox): Add options to clear search and selected value after item selection #1627 )
📝 (Feature) Finalize InputGroup component --> needs revisit (handle input element corner rounding via props, not via css cascade), decision what it should be, then finalize (medium)
📝 (Feature) Notification Manager. Maybe use a lib for the management part, must work with our PortalProvider/must not break in shadowroot. Separate manager and visual component. Manager is headless, doesn't render components, only as children or in slots. (implement in Aurora first) (complex) Prio 1
(Feature) Allow passing a specific z-index for portal root to AppShell to override the default --> needs research regarding effects, probably we'll need to have custom z-index on all (or most) components which have a z-index (easy/medium) Prio 3
Add option to clear contents/value to TextInput(currently exists for SearchInput only, ensure consistency between the two)
Handle whitespace / breaking behaviour in DataGrid cells (sensible default to handle word breaking when necessary, provide additional props to help fine-tune whitespace and wordbreaking (also allow for elipsis overflow?)
Design / Introduce a column layout component (using grid internally)
Make Select / ComboBox menus discernable from backgrounds (when a menu opens over some background colors or over a text input, it becomes almost invisible)
Properly handle vertical overflow on SideNavigation items (remove fixed height), don't center align labels, properly name classes (.level-2 -> juno-sidenavigation-item-lvl-2), doule-check width / behaviour in conjunction with current and future AppShell behaviour (Will be fixed with completion of [Task](ui): fix SideNavigation problems #1573 )
design an implement a spacing utility that accepts numeric tw-spacing tokens, a spacing mechanism (padding, margin, gap, …?), and direction (left, bottom, right, top, x, y, all), and returns a tw-class that can be used directly by the component calling it. Goal is to keep our spacing systematic and consistent.
📝 (Bug) When NativeSelectionGroup is disabled, the dropdown doesn't disable the default value. Disabled only appears on click. And default value sometimes dissapears. (medium)
📝 (Inconsistency) Look into simplifications for Select/ComboBox regarding super flexible API allowing value/label/ --> evaluation + decision needed --> all topic regarding simplification of these components: first look into new stylable native select options (medium/complex) Prio 2
📝 (Inconsistency)Unification of tightly connected components, specifically those where children don't make sense to use standalone and tests for the parent can't be written without the children. Decide on whether we want to use "Dot-notation" for tightly coupled parent/child components or no --> evaluate and design architecture. Also look into grouping stories for parents and their subcomponents into one (new tab nav feature in storybook)(medium) Prio 2
(Inconsistency) Type improvements: rather than going over the whole codebase we're improving this bit by bit triggered by user feedback. Starting with the already known topics (modal header, Pagination, ...) (incremental) Prio 3
(Inconsistency) API inconsistencies: same as above, will start with known inconsistencies in specific components, and then as we go (title, heading, spacing, unpad, disable/disabled) (incremental) Prio 3
Non-prioritized
(Improvement) Message: Update layout, replace gradient background, and reduce spacing
Not ready for implementation
(Feature) Stack: add spacing boolean prop to add standard gap spacing value (similar to the ones on the Container component) --> consistency topic, affects more than Stack --> needs design/decision, combine with unpad prop refactor for Box component (not ready) (easy)
(Inconsistency) Address all type casting in components with "as" --> clarify
📝 (Inconsistency) Check storybook code examples for stories for errors and fix. e.g. code that doesn't work at all when you try to use it, code where tw classnames with jn: prefix are used, manually written code example that doesn't match the story anymore (easy) Prio 1
📝 (Feature) DataGrid Row hover/active state (plus prop to toggle hover/active behaviour) --> check with Martin about design, otherwise use Supernova implementation (easy) Prio 1
Description
Collection of all known roadmap items for juno-ui-components, prioritized.
Priority 0
Priority 1
SignInFormcomponent #1439Form: new proprequired(working title) which renders a legend explaining what the required indicator does (easy) Prio 1DescriptionListwith child components #1172global.cssandtheme.css(the CSS variables and global styles are duplicated, one is used for ui component styles and the other is exported to be used as theme basis in apps). It should be possible to extract the common pieces into a separate css file that both import to remove the duplicationTextInput type="password"#1468Not ready for implementation
📝 (Improvement)
DataGridToolbar:Toolbarcomponent which isn't tied to theDataGrid(Improvement)
Badgecomponent should nicely display single-digit or low digit numbers. Maybe needs a new component --> researchUpload Dialog (no new component yet, UX pattern only for now)
(Feature) ComboBox: Discuss and decide whether we want to introduce a generically useable mechanism to allow developers to clear ComboBox immediately after changing/ selecting a value, as is needed in filters with immediate effect where we want users to be able to select another filter suing the same ComboBox. ([Feature](ComboBox): Add options to clear search and selected value after item selection #1627 )
📝 (Feature) Finalize InputGroup component --> needs revisit (handle input element corner rounding via props, not via css cascade), decision what it should be, then finalize (medium)
📝 (Theme) SAP on brand experience --> concept work needed (design and technical) (medium?) Prio 1
[ ]❓(Improvement) React19 optimization, mostly related to useEffects --> research, POC, concept needed Prio 1
📝 (Feature) Notification Manager. Maybe use a lib for the management part, must work with our PortalProvider/must not break in shadowroot. Separate manager and visual component. Manager is headless, doesn't render components, only as children or in slots. (implement in Aurora first) (complex) Prio 1
(Feature) Allow passing a specific z-index for portal root to AppShell to override the default --> needs research regarding effects, probably we'll need to have custom z-index on all (or most) components which have a z-index (easy/medium) Prio 3
📝 (Improvement/Breaking) Don't bundle webfonts into the ui-components package anymore --> solution needed (medium)
Add option to clear contents/value to
TextInput(currently exists forSearchInputonly, ensure consistency between the two)Handle whitespace / breaking behaviour in DataGrid cells (sensible default to handle word breaking when necessary, provide additional props to help fine-tune whitespace and wordbreaking (also allow for elipsis overflow?)
Design / Introduce a column layout component (using grid internally)
Make
Select/ComboBoxmenus discernable from backgrounds (when a menu opens over some background colors or over a text input, it becomes almost invisible)Properly handle vertical overflow on SideNavigation items (remove fixed height), don't center align labels, properly name classes (
.level-2->juno-sidenavigation-item-lvl-2), doule-check width / behaviour in conjunction with current and future AppShell behaviour (Will be fixed with completion of [Task](ui): fix SideNavigation problems #1573 )design an implement a spacing utility that accepts numeric tw-spacing tokens, a spacing mechanism (padding, margin, gap, …?), and direction (left, bottom, right, top, x, y, all), and returns a tw-class that can be used directly by the component calling it. Goal is to keep our spacing systematic and consistent.
Priority 2
Not ready for implementation
Backlog
Cardcomponent #1332Not ready for implementation
Non-prioritized
Not ready for implementation
unpadprop refactor forBoxcomponent (not ready) (easy)Done
jn:prefix are used, manually written code example that doesn't match the story anymore (easy) Prio 1Cardcomponent needed --> design needed, container only (for now), conceptual/semantic differentiation toBox(medium) Prio 1 - AuroraPageHeader:mr-3margin-right from base styles; add explicit spacing at all affected usage sites in ui-components and apps — PR fix(ui): remove hardcoded margin-right from Spinner component #1676xssize variant — closes [Task](ui): Add extra-small size to Button component #1638, PR feat(ui): add extra-small size to Button component #1644Additional Notes
New Proposals:
DescriptionListwith child components #1172 (comment)