Skip to content

style(Tooltip): changed tooltip font#834

Closed
Pratik-050 wants to merge 6 commits intolayer5io:masterfrom
Pratik-050:custom_tooltip_font_change
Closed

style(Tooltip): changed tooltip font#834
Pratik-050 wants to merge 6 commits intolayer5io:masterfrom
Pratik-050:custom_tooltip_font_change

Conversation

@Pratik-050
Copy link
Copy Markdown

Notes for Reviewers
Changed font for the CustomTooltip component.

This PR fixes #

Screenshot from 2024-12-03 00-04-05

Screenshot from 2024-12-03 00-03-53

Signed commits

  • Yes, I signed my commits.

Signed-off-by: Pratik Chandra Pal <pratikpal050@gmail.com>
Comment on lines +18 to +21
const StyledFontWrapper = styled(Typography)(() => ({
fontFamily: ['Qanelas Soft Regular'].join(',')
}));

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use the typography from the theme. take a theme as a props in the typography

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes i already told yesterday pass variant not font family

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @amitamrutiya @sudhanshutech here we can't use this approach:

const StyledFontWrapper = styled(Typography)(({theme}) => ({
typography: theme.typography.textH2Regular,
}));

cause the styled component is being imported from the mui library, and the theme tokens are also coming from mui Typography api. So they'll take the default font of MUI which is Roboto.
I've already tried that.

@leecalcote
Copy link
Copy Markdown
Member

Designs, not Patterns.

sudhanshutech and others added 3 commits December 5, 2024 18:07
Signed-off-by: Sudhanshu Dasgupta <dasguptashivam23@gmail.com>
Signed-off-by: Md Kaif Ansari <amdkaif843@gmail.com>
Signed-off-by: Sudhanshu Dasgupta <dasguptashivam23@gmail.com>
@Pratik-050 Pratik-050 closed this Dec 5, 2024
@Pratik-050
Copy link
Copy Markdown
Author

Problem with merge conflicts. Closing!

ITACHI161105 pushed a commit to ITACHI161105/sistent that referenced this pull request Apr 24, 2026
…erage

Pulls in the 10 canonical camelCase wire keys added in meshery/schemas PR
layer5io#834 (MesheryPattern / Design counts, designType, TeamMember.joinedAt,
Schedule.lastRun / nextRun). No source changes in this commit — the
consuming flips land in the follow-up.

Signed-off-by: Lee Calcote <lee.calcote@layer5.io>
ITACHI161105 pushed a commit to ITACHI161105/sistent that referenced this pull request Apr 24, 2026
…e 2.K cascade)

Completes the Option B Phase 2.K cascade now that meshery/schemas PR layer5io#834
(v1.2.0) publishes the canonical camelCase wire keys. Surgical field-rename
only — no behavioural or structural changes.

Flips (46 sites across 9 files):
  • view_count        → viewCount         (MesheryPattern / Design v1beta3)
  • download_count    → downloadCount     (MesheryPattern / Design v1beta3)
  • clone_count       → cloneCount        (MesheryPattern / Design v1beta3)
  • deployment_count  → deploymentCount   (MesheryPattern / Design v1beta3)
  • share_count       → shareCount        (MesheryPattern / Design v1beta3)
  • design_type       → designType        (MesheryPattern / Design v1beta3)
  • joined_at         → joinedAt          (TeamMember / Team v1beta2)
  • last_run          → lastRun           (Schedule v1beta2)
  • next_run          → nextRun           (Schedule v1beta2)

Intentionally NOT flipped in this PR (documented inline with TODOs):
  • team_name (src/custom/Workspaces/types.ts) — deferred until meshery-cloud
    renames the SQL alias on Team; flipping without the server rename would
    break the wire.
  • team_ids / team_names (src/custom/TeamTable/TeamTableConfiguration.tsx)
    — deferred until the meshery-cloud bulk-delete handler lands dual-accept
    (camel + legacy snake) to avoid a client-only flip breaking the POST body.

Refs: meshery/schemas#832 (closed), meshery/schemas#834 (canonical coverage, merged)
Signed-off-by: Lee Calcote <lee.calcote@layer5.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants