Skip to content

chore(*): update changelog #12383

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

Merged
merged 2 commits into from
Dec 1, 2022
Merged

chore(*): update changelog #12383

merged 2 commits into from
Dec 1, 2022

Conversation

SisIvanova
Copy link
Collaborator

Related to IgniteUI/igniteui-theming/issues/55

Additional information (check all that apply):

  • Bug fix
  • New functionality
  • Documentation
  • Demos
  • CI/CD

Checklist:

  • All relevant tags have been applied to this PR
  • This PR includes unit tests covering all the new code (test guidelines)
  • This PR includes API docs for newly added methods/properties (api docs guidelines)
  • This PR includes feature/README.MD updates for the feature docs
  • This PR includes general feature table updates in the root README.MD
  • This PR includes CHANGELOG.MD updates for newly added functionality
  • This PR contains breaking changes
  • This PR includes ng update migrations for the breaking changes (migrations guidelines)
  • This PR includes behavioral changes and the feature specification has been updated with them

Sorry, something went wrong.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@SisIvanova SisIvanova added the ❌ status: awaiting-test PRs awaiting manual verification label Nov 25, 2022
@SisIvanova SisIvanova requested a review from simeonoff November 25, 2022 12:37
$secondary-color: #f96a88;
$surface-color: #e1ebe4;
// Additional colors
$error-color: color($light-fluent-palette, 'error');
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if it's possible to migrate this type of calls:

$app-palette: palette($primary: $primary, $secondary: $secondary, $grays: $grays);
@include dark-theme(
    $palette: $app-palette,
    $exclude: map-keys(map-remove($components, $include...),)
);

to this:

$app-palette: palette($primary: $primary,
  $secondary: $secondary,
  $grays: $grays,
  // auto-migrated to material dark based on dark-theme preset call
  $error: color($dark-material-palette, 'error'),
  $warn: color($dark-material-palette, 'warn'),
  $info: color($dark-material-palette, 'info'),
  $success: color($dark-material-palette, 'success')
);
@include dark-theme(
    $palette: $app-palette,
    $exclude: map-keys(map-remove($components, $include...),)
);

Copy link
Member

Choose a reason for hiding this comment

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

Just to mention that the same thing happened with the greys in one of the previous updates and wasn't auto-migrated, so we have to think about how to handle these cases automatically.

Copy link
Member

Choose a reason for hiding this comment

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

@SisIvanova I'm not sure if you should answer this question. Your PR is ready for merge, but since there's a hanging discussion here, I would like to get an answer prior to merging it, so it doesn't get lost.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@kdinev Yes, we are planning to provide fallback values for these colors and it should be done soon.

Copy link
Member

Choose a reason for hiding this comment

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

@SisIvanova So, if there's going to be a default fallback, then a migration would not be needed, I guess?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@kdinev Yes, no migration is needed.

@kdinev kdinev added 📖 documentation ✅ status: verified Applies to PRs that have passed manual verification and removed ❌ status: awaiting-test PRs awaiting manual verification labels Nov 28, 2022

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@kdinev kdinev merged commit 551d27e into master Dec 1, 2022
@kdinev kdinev deleted the sivanova/update-changelog branch December 1, 2022 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📖 documentation ✅ status: verified Applies to PRs that have passed manual verification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants