Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat(chip): add recipe and variables#30873

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
thetaPC wants to merge12 commits intoionic-modular
base:ionic-modular
Choose a base branch
Loading
fromFW-6833
Draft

Conversation

@thetaPC
Copy link
Contributor

Issue number: resolves #


What is the current behavior?

What is the new behavior?

Does this introduce a breaking change?

  • Yes
  • No

Other information

@vercel
Copy link

vercelbot commentedDec 15, 2025
edited
Loading

The latest updates on your projects. Learn more aboutVercel for GitHub.

ProjectDeploymentReviewUpdated (UTC)
ionic-frameworkReadyReadyPreview,CommentDec 18, 2025 2:17am

Choose a reason for hiding this comment

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

Do we need Sass variables for this? I feel like it just adds another layer when the CSS variables would do

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I created it so we don't have such long variables cluttering the base file. Thoughts?

};

typeComponents={
IonChip?:{

Choose a reason for hiding this comment

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

Do you think we should keep these interfaces in the component's folder to keep it better organized? Or is this something we might move later and combine between components?

Comment on lines 95 to 96
paddingVertical:'6px',
paddingHorizontal:'12px',

Choose a reason for hiding this comment

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

Suggested change
paddingVertical:'6px',
paddingHorizontal:'12px',
padding:{
vertical:'6px',
horizontal:'12px',
}

Would it not be cleaner to do it as objects?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

brandyscarney reacted with thumbs up emoji

Choose a reason for hiding this comment

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

Looks good. We might want to move totop,end,start andbottom for all components for consistency but we can tackle that when we get there.

Choose a reason for hiding this comment

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

A lot of these values are hardcoded - why aren't we using the design tokens like this:

--ion-scaling-xxs--ion-scaling-xs--ion-scaling-smetc

},

avatar:{
size:`${24/fontSizes.chipBase}em`,

Choose a reason for hiding this comment

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

These numbers seem made up - maybe we need to define these calculations better?

}

constfontSizes={
chipBase:14,

Choose a reason for hiding this comment

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

Why is the base 14 for Chip? Shouldn't all components have the same base size?

Choose a reason for hiding this comment

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

My comments on the md file apply here as well

thetaPCand others added3 commitsDecember 15, 2025 16:50
Co-authored-by: Brandy Smith <brandyscarney@users.noreply.github.com>
Co-authored-by: Brandy Smith <brandyscarney@users.noreply.github.com>
Co-authored-by: Brandy Smith <brandyscarney@users.noreply.github.com>
Co-authored-by: Brandy Smith <brandyscarney@users.noreply.github.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@brandyscarneybrandyscarneybrandyscarney left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

package: core@ionic/core package

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@thetaPC@brandyscarney

[8]ページ先頭

©2009-2025 Movatter.jp