Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract component styles to core #5282

Open
wants to merge 10 commits into
base: develop
Choose a base branch
from
Open

Conversation

epetrow
Copy link
Contributor

@epetrow epetrow commented Jan 7, 2025

closes: #305

@epetrow epetrow changed the title chore: extract component styles to core WIP: Extract component styles to core Jan 7, 2025
@epetrow epetrow force-pushed the extract-component-styles branch 5 times, most recently from d7dba3d to 6265b23 Compare January 9, 2025 11:15
@epetrow epetrow self-assigned this Jan 9, 2025
@epetrow epetrow force-pushed the extract-component-styles branch 9 times, most recently from ce716a6 to b13c1d1 Compare January 13, 2025 12:55
@epetrow epetrow marked this pull request as ready for review January 13, 2025 13:00
@epetrow epetrow requested a review from a team as a code owner January 13, 2025 13:00
@epetrow epetrow changed the title WIP: Extract component styles to core Extract component styles to core Jan 13, 2025
@epetrow epetrow added this to the 2025 Q1 (Feb) milestone Jan 13, 2025
@epetrow epetrow force-pushed the extract-component-styles branch from b13c1d1 to f33b7b6 Compare January 13, 2025 14:32
@zhpenkov zhpenkov self-requested a review January 14, 2025 12:52
@epetrow epetrow force-pushed the extract-component-styles branch from f33b7b6 to bef60c4 Compare January 14, 2025 16:42
@epetrow epetrow force-pushed the extract-component-styles branch from 3274f76 to 3652014 Compare January 14, 2025 17:01
}

// RTL
.k-rtl,
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be scoped to k-tabstrip.

This is fixed in develop, it seems like some of the theme and layout files of the components in this core modules are applied from a stale develop branch, and some recent changes are missing.

We should carefully look at the differences between develop and this branch output styles and update the core module component files accordingly.

@zhpenkov
Copy link
Contributor

ab83343
We should consider generating our metadata/docs from the core in the future to reduce maintenence.
As of now, it is not possible as the script needs to be adjusted.

@@ -46,6 +46,8 @@
// Spacing
$_default-spacing: $kendo-spacing,
$kendo-spacing: $kendo-spacing !default,
$kendo-use-input-button-width: false !default,
$kendo-use-input-spinner-width: false !default,
Copy link
Contributor

Choose a reason for hiding this comment

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

These input variables seem too out of place to me.

I would suggest moving them to the component variables.
Or define them globally per-theme.

@@ -88,6 +88,42 @@ $kendo-theme-colors: (
),
) !default;

@forward "@progress/kendo-theme-core/scss/color-system/_swatch-legacy.scss" with (
$kendo-body-bg: $kendo-body-bg,
$kendo-body-text: $kendo-body-text,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this @forward necessary in Fluent?
And the other themes?

@inikolova inikolova self-requested a review January 20, 2025 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants