You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Properties which have a function type should fail the no-incompatible-property-type rule unless a custom converter is provided. For example, this should fail as String certainly will not result in a valid conversion:
@property()publicfuncProp?: ()=>void;
For function properties, only including a custom converter or {attribute: false} should pass the rule.
The text was updated successfully, but these errors were encountered:
I also noticed that Record<...> types also pass with the default String converter, and they certainly should not.
steverep
changed the title
Function properties should fail no-incompatible-property-type
Function and Record properties should fail no-incompatible-property-type
Jan 21, 2024
Properties which have a function type should fail the
no-incompatible-property-type
rule unless a custom converter is provided. For example, this should fail asString
certainly will not result in a valid conversion:For function properties, only including a custom converter or
{attribute: false}
should pass the rule.The text was updated successfully, but these errors were encountered: