The actual problem is that we are using insertKey from a OperationM instead of just importing it from the global scope. - This is no longer an issue because it was fixed when migrating the entire set of models to pure data models #174. However back then I was not sure if we need string or enum. Now with the benefit of more reading I understand that we can move these constants to enums because there are only 3 types of ops: insert, delete, retain.
For further clarification: Embeds are stored as data types on the insert ops. So that means the ops types are just 3 known types. I specify this because at some point we got a little confused by thinking that the ops types can be more than 3 (inlcuding custom emebds) That is false because embeds are store in the data of an operation, not in the key.
The actual problem is that we are using insertKey from a OperationM instead of just importing it from the global scope.- This is no longer an issue because it was fixed when migrating the entire set of models to pure data models #174. However back then I was not sure if we need string or enum. Now with the benefit of more reading I understand that we can move these constants to enums because there are only 3 types of ops: insert, delete, retain.For further clarification: Embeds are stored as data types on the insert ops. So that means the ops types are just 3 known types. I specify this because at some point we got a little confused by thinking that the ops types can be more than 3 (inlcuding custom emebds) That is false because embeds are store in the data of an operation, not in the key.