Relax record id validation

[leplatrem]

Do we really need to ensure that posted record ids match a uuid regex?

We can generate a uuid when a record without id is posted, and leave the usage of uuid in our official clients.
But is there any reason to use a different regex that collection and bucket names?

edit: The usecase is the Web sync extension chrome.storage.sync: since any key is accepted, it takes the md5 of the key to "generate" UUIDs. Instead we could let the client push any key as record id.

• Related Should we return 409 instead of 200 for POST if specified id already exists ? #140

[Natim]

I agree with your analysis, the main reason why we did that is to let people create IDs on client side without having to worry about conflicts.

Also we have a strategy to generate a UUID from another string (using the md5 approach).

But I agree with you that we should let people use something else if need be.

[glasserc]

Ultimately, you need the client to choose the ID, but I don't think it needs to always be a UUID. I would be 👍 on relaxing the requirement.