search Identifiers for meilisearch and probably others need to be checked

If you use a document with the ID foo.bar, it will cause issues because meilisearch does not support . in identifiers: https://www.meilisearch.com/docs/learn/getting_started/primary_key#formatting-the-document-id

However, other search engines do. For compatibility, I guess the marshaller would need to normalize these identifiers. What do you think?

Oct 02 '24 16:10 Toflar

The . is also object separetor for the internal flattenmarshaller or nested object conditions. I think we may shoud prevent that chars and only support a-z, A-Z and _ to support camel or snake case field names. Would that be a big problem in your case?

Oct 03 '24 20:10 alexander-schranz

No not at all. That's why I asked :) We should just make sure that the identifiers we allow work on all platforms so switching is easy :)

Oct 03 '24 20:10 Toflar

#427 forces field names with a-z, A-Z, 0-9, _ all fields need to start with a-z, A-Z currently.

Oct 06 '24 11:10 alexander-schranz