We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
forms
Yes
I think this was actually fixed: #28948
I didn't quite understand from the above what we were meant to do.
But are we meant to include an extra attribute somewhere here:
<!-- label --> <mat-label> {{entry.key | getAllowanceKey: false}} Allowance Basis </mat-label> <!-- select --> <mat-select id="allowanceBasis-hardware-{{$index}}" formControlName="allowanceBasis" required> <mat-option>-- None --</mat-option> @for (allowanceBasisType of AllowanceBasisTypes | sortAlphabetical; track allowanceBasisType) { <mat-option [value]="allowanceBasisType">{{allowanceBasisType | replaceUnderscores | titleCase}}</mat-option> } </mat-select>
to prevent this:
Thank you
Please see above
See above
ng version
No response
No
The text was updated successfully, but these errors were encountered:
You shouldn't have to do anything for the fix from #28948. Maybe you aren't on the right version? The fix was released in 17.3.6.
Sorry, something went wrong.
I'm on "@angular/core": "^17.3.2", and I get this:
How do I upgrade?
That's working as expected since now it's being flagged as an informational message, not an error.
No branches or pull requests
Which @angular/* package(s) are the source of the bug?
forms
Is this a regression?
Yes
Description
I think this was actually fixed: #28948
I didn't quite understand from the above what we were meant to do.
But are we meant to include an extra attribute somewhere here:
to prevent this:
Thank you
Please provide a link to a minimal reproduction of the bug
Please see above
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)No response
Anything else?
No
The text was updated successfully, but these errors were encountered: