feat(angular): add booleanAttribute transform to IonItem inputs #30825
+690
−252
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements
booleanAttributetransforms for IonItem's boolean inputs, allowing cleaner syntax as requested in #30822.Problem
Currently, Angular developers have to use explicit bindings for boolean attributes:
This generates IDE warnings and is more verbose than the desired syntax.
Solution
Applied Angular's
booleanAttributetransform to IonItem'sbutton,detail, anddisabledinputs. This allows:Changes
@stencil/angular-output-targetfrom^0.10.0to^1.1.1IonItemcomponent in both regular and standalone Angular proxiesbutton,detail, anddisabledfrom@ProxyCmpand@Componentinputs arrays@Input({ transform: booleanAttribute })decorators with getters/settersTesting
✅ Core package builds successfully
✅ Angular package builds successfully
✅ Standalone package builds successfully
✅ All linting checks pass
✅ TypeScript compilation without errors
✅ No breaking changes to existing API
Type of Change
Closes #30822