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

Input & Textarea: emit kirbyChange on value change #3874

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

Conversation

lydemann
Copy link
Collaborator

@lydemann lydemann commented Mar 19, 2025

Which issue does this PR close?

This PR closes #3793

What is the new behavior?

Make counter update with reactive forms

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

  • Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
  • 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.

@RasmusKjeldgaard RasmusKjeldgaard added the fix Add this PR to the changelog as a bugfix label Mar 19, 2025
@RasmusKjeldgaard RasmusKjeldgaard changed the title fix: emit kirbyChange on formcontrol value change Input & Textarea: emit kirbyChange on value change Mar 19, 2025

// eslint-disable-next-line @typescript-eslint/no-unused-vars
registerOnChange(_fn: any): void {
// handled in textarea Angular component
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
// handled in textarea Angular component
// handled by built-in textarea support in Angular


// eslint-disable-next-line @typescript-eslint/no-unused-vars
registerOnTouched(_fn: any): void {
// handled in textarea Angular component
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
// handled in textarea Angular component
// handled by built-in textarea support in Angular


// eslint-disable-next-line @typescript-eslint/no-unused-vars
setDisabledState?(_isDisabled: boolean): void {
// handled in textarea Angular component
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
// handled in textarea Angular component
// handled by built-in textarea support in Angular

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix Add this PR to the changelog as a bugfix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Input counter not fully working with ReactiveForms
3 participants