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
letw='qq';letr={x: 1,[w+'ee']: 2};console.log(r);// result will be "{ x: 1, qqee: 2 }"
I'm not sure this will work correctly in Camo schema definition, but as long as class constructors work synchronously, this must work.
Anyway i don't see schema definitions in your example. It has two syntax errors: no comma after second line and missing of closing brace at seventh one. But this isn't main: you are asking about schema providing instance.
If you have some field defined as Object inside your schema, there will not be any issues with using of computable keys in it, considering there are no documents with fields referenced to computable key until key is computed and persistently saved.
You are free to do this way (will insert initial data but not more, as long as $userId is variable and is computed only once to determine key to use, so any next inserts will fail with "key exists" error):
Hi,
Thank your for this great project.
I have just one functional question, I have a dynamic key like :
$userId is a dynamic key, so i cant define it on my model schema.
I dont know if we can do this with camo our we need to implement it manualy ?
Thank's
The text was updated successfully, but these errors were encountered: