[Bug] Inconsistent: newId() can't be assigned directly as id, but can be used directly in .byId()

[ptpaterson]

Hi @Mike This looks like a duplicate of this recent topic:

newId() cannot be used directly as an id

This might be by design, but felt unexpected nonetheless. If for some reason you would like to create an id with the newId() method this cannot be used directly as the value for the id of a new document. let id = newId() testCollection.create({ id: id, created: Time.now() }) It will return a type error: invalid_type error: Value at `id` has type ID, which cannot be persisted. If you would add it as a string, it does work: let id = newId() testCollection.create({ id: "#{id}", create…

We have an internal ticket to extend the the create method to accept ID. Note my response in that topic, since there is rarely a reason (thank you for providing an example!) to perform MyColl.create({ id: newId(), ... }); the process that hands out keys for newId is the same one that auto-generates ids when you don’t provide an id field.

The byId method can already accept String | Int | ID. It does look like docs need updated, though, so I will pass that on.

Thanks, as always, for your feedback! Keep it coming