Properties shouldn't be reset by any value

[Mouvedia]

@container object1 {
    background: whatever;
}
state
{
    isA: object2, object1;
}
@container object2 {
    background: #0;
}

expected result:
black
current result:
white

Since there are no @value whatever { } found in the HSS file: the "whatever" value should be considered invalid and the declaration ignored (hence not resetting the one in the previous object). It shouldn't be completely discarded because you could for example dynamically import another HSS file (which would contain the definition of the missing @value).

Short: ignore it but re-evaluate it for the inspector (edit) or file importation (addition).

affected: v0.48.1.49

[princezuda]

If we are going to not discard the invalid data, then we need to use something like expect: whatever, we, me, ever;. That way If the variable is not in another HSS file then the missing expected values should be discarded. expect: would simply be a way to keep values that aren't assigned to anything waiting. There are potential issues with this, but those won't appear until 0.6 when we start to use JS. We should not allow any input fields to use expect:, because that is just asking for a nightmare.

[Mouvedia]

Again you can't discard anything unless it's somehow recoverable because for example you could dynamically import an HSS file which could have the referenced @value object name.

This is just an implementation detail anyway: what matters is that an invalid or unreferenced value must be ignored.