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
The .remoteCid flag, introduced pre-v0.2.0, is a way to signal if the entity exists remotely or not. However, when casting between entities, especially higher-level entities as exposed by rlay-ontology packages, the default absence of the .remoteCid flag causes ugly code. E.g.
newEntity.remoteCid = oldEntity.remoteCid
As @hobofan suggested, the presence of such a flag may just be cosmetically and not necessary for any of the methods (e.g. assert) to work properly. As a first instance we will therefore try to remove the .remoteCid flag to see if any behavior changes occur.
As a second step, the entity could hold state about which assertions it pass through to the client to optimize some of its behaviors
The text was updated successfully, but these errors were encountered:
The
.remoteCid
flag, introduced pre-v0.2.0, is a way to signal if the entity exists remotely or not. However, when casting between entities, especially higher-level entities as exposed byrlay-ontology
packages, the default absence of the.remoteCid
flag causes ugly code. E.g.As @hobofan suggested, the presence of such a flag may just be cosmetically and not necessary for any of the methods (e.g.
assert
) to work properly. As a first instance we will therefore try to remove the.remoteCid
flag to see if any behavior changes occur.As a second step, the entity could hold state about which assertions it pass through to the client to optimize some of its behaviors
The text was updated successfully, but these errors were encountered: