Also, right now the current API doesn’t let them change the options of an existing entity at all
This isn’t guaranteed to be the case forever.
so you wouldn’t lose any functionality with an
addthat just left the opts as-is for an existing entity when the caller left them off… if they wanted the opts updated on an existing entity, they’d provide the opts, which would be additional functionality.
If the default functionality is “keep the existing value” then it doesn’t work for creating new components (because there is no existing value yet). And we cannot have two different default functionalities for the same function, based on a runtime conditional. That would be very bad.
