Skip to content

test(forms): cover transformedValue without FormField context#67325

Open
sonukapoor wants to merge 1 commit intoangular:mainfrom
sonukapoor:test/transformed-value-standalone-parse-errors
Open

test(forms): cover transformedValue without FormField context#67325
sonukapoor wants to merge 1 commit intoangular:mainfrom
sonukapoor:test/transformed-value-standalone-parse-errors

Conversation

@sonukapoor
Copy link
Contributor

@sonukapoor sonukapoor commented Feb 26, 2026

Adds a test verifying that transformedValue exposes parse errors via the returned signal's parseErrors() property when no FormField context is present.

This ensures that:

  • parse errors are still observable without DI-based field propagation
  • the model is not updated when parse omits value
  • valid input clears parse errors and updates the model

This test protects the documented contract that DI-based error propagation is expected for FormValueControl usage, while standalone usage relies on explicit consumption of parseErrors().

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Adds a test verifying that `transformedValue` exposes parse errors via
the returned signal's `parseErrors()` property when no FormField
context is present.

This ensures that:
- parse errors are still observable without DI-based field propagation
- the model is not updated when `parse` omits `value`
- valid input clears parse errors and updates the model

This test protects the documented contract that DI-based error
propagation is expected for FormValueControl usage, while standalone
usage relies on explicit consumption of `parseErrors()`.
@pullapprove pullapprove bot requested a review from JeanMeche February 26, 2026 15:40
@ngbot ngbot bot added this to the Backlog milestone Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant