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
Currently, the compiler treats getters and setters identically to props; the implementations present on a component are dropped. (In the example above, neither 'getter' nor 'setter' are ever logged to console.) This behavior is not obvious, but using @wire on a getter/setter is also kind of weird. (A getter cannot receive data, so decorating it with a data provider doesn't really make sense.) To make the behavior more consistent with expectations, we should either disallow @wire on a getter/setter, or we should preserve their implementations. In either case, it would be a breaking change.
The text was updated successfully, but these errors were encountered:
Currently, the compiler treats getters and setters identically to props; the implementations present on a component are dropped. (In the example above, neither
'getter'
nor'setter'
are ever logged to console.) This behavior is not obvious, but using@wire
on a getter/setter is also kind of weird. (A getter cannot receive data, so decorating it with a data provider doesn't really make sense.) To make the behavior more consistent with expectations, we should either disallow@wire
on a getter/setter, or we should preserve their implementations. In either case, it would be a breaking change.The text was updated successfully, but these errors were encountered: