Computed properties in components seem to be leaking state

@Juraci wrote:

In this Twiddle I created a simple example of a component that has a computed property. The application controller simulates a model that has 2 instances and those instances are each passed to the component as a simple parameter. What I expected from this experiment was to have the first rendered component with the activity count as 1 and the other as 0.

living room - Activity 1
bedroom - Activity 0

but the actual result is

living room - Activity 1
bedroom - Activity 1

Am I missing something here? Thanks in advance.

Posts: 2

Participants: 2

Read full topic