Enum component variant - assign vs query (interaction)

[soanvig]

I have a general question to improve my understanding of Bevy.

When I spawn an entity I want it to be interactive (hence Interaction enum):

commands.spawn((SomeEntity { ... }, Interaction::None));

I cannot use Interaction enum directly, so I need to add enum variant.
However, when I run a query on it:

Query<&Interaction, Changed<Interaction>>

I can also match that entity against any Interaction I want (having both ::Hovered and ::Pressed working).

Both of these examples make sense individually, but together it's a bit counterintuitive design to me. Could somebody elaborate on topic of enum variants as components? From my experiment it doesn't matter which enum variant of Interaction I add to an entity, it gives me all Interaction capabilities.

[soanvig]

After further investigation I discovered, that what I set as a component (Interaction) becomes initial value of the enum type component in a given entity. It doesn't prevent the enum to take other variants. It makes sense now.

Initially I thought that by adding Interaction::Pressed I "allow entity to be pressed", but that's wrong understanding. Instead I allow entity to be "Interaction" with ::Pressed being the initial value..