Replace Roboto Font with Qanelas Soft Font

[senali-d]

Notes for Reviewers

This PR fixes #8863

Signed commits

• Yes, I signed my commits.

[Chadha93]

@senali-d I think you missed pushing the font changes...

[senali-d]

@senali-d I think you missed pushing the font changes...

@Chadha93
What I have done here is instead of "@mui/material" Chip component import the @material-ui/core Chip.

Reason:
We have already define font-family in custom theme file. So it is override @material-ui/core component fronts but not the "@mui/material".
So when use @material-ui/core component no need to override the component level styles. Theme file apply here and override the MUI styles.

[Chadha93]

@senali-d I think you missed pushing the font changes...

@Chadha93 What I have done here is instead of "@mui/material" Chip component import the @material-ui/core Chip.

Reason: We have already define font-family in custom theme file. So it is override @material-ui/core component fronts but not the "@mui/material". So when use @material-ui/core component no need to override the component level styles. Theme file apply here and override the MUI styles.

Right, I meant, will this change the font to all the components in Meshery UI? Yes, we've defined it in the theme. ✔️

[senali-d]

Right, I meant, will this change the font to all the components in Meshery UI? Yes, we've defined it in the theme. ✔️

Ok I'll check other components as well.

[hamza-mohd]

Aligning the project on the typography used in the design system will certainly give Meshery more polish.

[saurabh100ni]

Let's discuss this on the Meshery dev call tomorrow,
Please add this as your agenda item in Docs: https://docs.google.com/document/d/1Dg4Uz9rGTuGHmYZwIt47z1j5x3LmnpxD1M1SgypAkQ0/edit

[leecalcote]

merge conflicts

[sudhanshutech]

Is it ideal to use core elements from mui. Since we need to move to mui V5 then again we have to revert these changes

[senali-d]

Actually this changes fixed theme defined fonts was not in using MUI components when we import it from MUI v5.

[senali-d]

Accidentally import MUI v5 components was fixed when we remove MUI v5 package. Is it possible?? // @aabidsofi19 @nebula-aac

Ref: #6888

[aabidsofi19]

Thanks @senali-d

[aabidsofi19]

After we remove all references to mui5 let's remove it from package.json

[senali-d]

After we remove all references to mui5 let's remove it from package.json

@aabidsofi19 Meshery ui already use MUI v5 icons. From the package @mui/icons-material so it depend on @mui/material. So we can't remove MUI v5 from package.json.

Note: Some of the icons are newly introduced in v5

[leecalcote]

Merge conflict, @senali-d

[senali-d]

@leecalcote Fixed conflicts

[leecalcote]

@senali-d it could have been something else, but I seem to get this crash when running this branch (on the dashboard):

[leecalcote]

@senali-d this item is in your court, I believe.

[senali-d]

@senali-d this item is in your court, I believe.

Yup, I think build issue is not relate to changes in this pr. I'll open a new pr for this.

[senali-d]

Recently Meshery UI is Migrate from MUI V4 to MUI V5. Ref: #9319
So once done it no need these changes. Use of the new theme of MUI v5 fill fix this issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[leecalcote]

@senali-d please push this over the line.