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

Deprecate standalone chip component #2391

Merged
merged 4 commits into from
Aug 5, 2022

Conversation

jkaltoft
Copy link
Collaborator

@jkaltoft jkaltoft commented Jul 4, 2022

Which issue does this PR close?

This PR closes #2341

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Are there any additional context?

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Reminders

  • Make sure you have implemented tests following the guidelines in: "The good: Test".
  • Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

Review

  • Do a self-review.
  • Request that the changes are code-reviewed
  • Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)

When the pull request has been approved it will be merged to develop by Team Kirby.

@jkaltoft jkaltoft linked an issue Jul 4, 2022 that may be closed by this pull request
4 tasks
@github-actions github-actions bot temporarily deployed to pr-2341-deprecate-standalone-chip-component July 4, 2022 11:56 Inactive
@github-actions github-actions bot temporarily deployed to pr-2341-deprecate-standalone-chip-component July 4, 2022 15:47 Inactive
@jkaltoft jkaltoft marked this pull request as ready for review July 4, 2022 20:09
@@ -7,6 +7,12 @@ import { ChangeDetectionStrategy, Component, HostBinding, Input } from '@angular
changeDetection: ChangeDetectionStrategy.OnPush,
})
export class ChipComponent {
constructor() {
console.warn(
'DEPRECATION WARNING: `<kirby-chip>` will be removed from the API in an upcoming major version of Kirby.'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we add a suggestion for migration to this issue? E.g. 'Use the kirby button component instead.'

@@ -7,6 +7,12 @@ import { ChangeDetectionStrategy, Component, HostBinding, Input } from '@angular
changeDetection: ChangeDetectionStrategy.OnPush,
})
export class ChipComponent {
constructor() {
console.warn(
'DEPRECATION WARNING: `<kirby-chip>` will be removed from the API in an upcoming major version of Kirby.'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
'DEPRECATION WARNING: `<kirby-chip>` will be removed from the API in an upcoming major version of Kirby.'
'DEPRECATION WARNING: `<kirby-chip>` will be removed from the API in Kirby v8.'

Consider being more specific, I think it makes the message a bit more helpful.

@jkaltoft jkaltoft merged commit 536d352 into release/v7.0.0 Aug 5, 2022
@jkaltoft jkaltoft deleted the 2341-deprecate-standalone-chip-component branch August 5, 2022 12:36
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.

Deprecate the standalone chip component
2 participants