NavIconItem some feature not available `Badge value` [5.0.0-beta.23]

[rpt-rfoxy]

Is your feature request related to a problem? Please describe.
CRM navigation has badge value on NavIconItem, wich mean its unavailable in current feature, i already try using component but it didnt match with the CRM UI,

screenshoot:

the current component only support dot Badge with props hasBadge
screenshoot:

Describe the solution you'd like
its will be good if we have badgeValue as props of NavIconItem.

Reference Link
CRM UI Figma

Story book example

[ss-dimasm]

Hi @rpt-rfoxy , thanks for raising this; I am unsure if it's available on the design specification but I've raise a query to them

for your reference https://www.figma.com/design/6CaivqdlTX0UkFYJkpBKDu?node-id=12289-31627#1229846743

[ss-dimasm]

Hi @rpt-rfoxy , got the reply from Design Team there's no design spec as it was never requested

any action that we could take to fulfill this request? @ksolanki7

[ss-dimasm]

from what I can see, the "badge value" in the attached CRM UI Figma is rendered from another component, which mean the NavIconItem should allow to accept a ReactNode

at this moment, to show the "badge" the NavIconItem have expose hasBadge API with a bool as the option; I think we could have a new prop called badge that allowing the user to pass ReactNode component while we're still have the hasBadge to render the "red dot"

[ksolanki7]

@rpt-rfoxy Thank you for raising this ticket, however, I believe the correct process would be to get this through from the Designer who worked on the Product design. For ABX's new CRM UI, it should be Ron Prince. I have already raised this concern over the Team's General channel under CRM Modernisation, and below is the message for reference.

Hello Ron Prince,
I’m following up on our recent discussion regarding the Icon with badge (including number), which appears to be missing from the current v5 Elements library. Have you had a chance to reach out to the Elements Design System team to review this and prepare a design for the development team?
As this component is required for the Top Navigation bar in the CM modernisation project, it would be helpful to understand the plan moving forward.
Additionally, could you advise on the preferred channel for raising such component-related gaps in v5 Elements that are essential for CM modernisation—would creating a Jira ticket be the appropriate approach?

In addition, thank you so much @ss-dimasm, looking into this.