Numbers not accepted as field names

[stasysdr]

When using patch.Document I get the following error:

Invalid property path "02.temperature". Unquoted property paths must match regex ([a-zA-Z_][a-zA-Z_0-9]*), and quoted property paths must match regex ((?:[^\\]|(?:\\.))+`)

The paths used are:

String documentPath = "test_collection/esp3/data/" + documentid.substring(len-20,len);

content.set("fields/00/mapValue/fields/temperature/integerValue", "21");

Firebase.Firestore.patchDocument(&fbdo, FIREBASE_PROJECT_ID, "" /* databaseId can be (default) or empty /, documentPath.c_str(), content.raw(), "00.temperature" / updateMask */)

It seems that regex ([a-zA-Z_][a-zA-Z_0-9]*) cannot extract field name if it does not begin with letters?

Any suggestions how to overcome this? I need to use "00", "02", "03" as field names for map fields.

Tried to encode with "%30%30" without success.

ESP8266
Firebase Client v4.1.0

[mobizt]

You should read the Firestore API reference for properly use.

A simple field name contains only characters a to z, A to Z, 0 to 9, or _, and must not start with 0 to 9. For example, foo_bar_17.

[stasysdr]

Thank you for the reference.
In another project python API accepts pure numbers as map field names, so I was hoping there is a workaround in ESP client as well.

[mobizt]

It's not issue and no workaround.

It's Google API design.

[stasysdr]

There is an issue with Google API design implementation then, as the reference is not followed in python API, and also in Firestore console.
Anyway, thanks for pointing out the reference limitations.

[mobizt]

It's not an issue in Google API. This is the Google Firestore REST API design as I post the link to Firestore REST API which is different from other Firebase Admin and SDK clients.

You should follow the APIs that google provided for supported platforms instead of assuming that all APIs are identical.

[mobizt]

You should know the difference of APIs when working on cross platforms even it worked on the same service.