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
I am a bit new to firebase but I have the following usecase.
A en entity has some public and private data, I can create a new entity within firecms by defining multiple fields.
Firebase doesn't support per field restrictions, but it does support restricting access per document.
The suggested solution in firebase is to create a collection named private, and restricting access to all documents within that collection.
In my use case I now have
a document at type/{id}
a private collection at type/{id}/private
and a single document at type/{id}/private/data
I am wondering if there is a way to configure FireCMS to map a field or a set of fields to this static document in the subcollection.
So the UI would show the fields as configured, and an additional section for fields in said document.
I am aware that FireCMS supports subcollections, but it looks like this feature is aimed at subcollections of variable size and generated ids.
Also, thanks for creating such an awesome tool, I was impressed by how easy it was to set up my workflow, and it does seem that I can extend the library easily.
Cheers
The text was updated successfully, but these errors were encountered:
I am a bit new to firebase but I have the following usecase.
A en entity has some public and private data, I can create a new entity within firecms by defining multiple fields.
Firebase doesn't support per field restrictions, but it does support restricting access per document.
The suggested solution in firebase is to create a collection named private, and restricting access to all documents within that collection.
In my use case I now have
a document at type/{id}
a private collection at type/{id}/private
and a single document at type/{id}/private/data
I am wondering if there is a way to configure FireCMS to map a field or a set of fields to this static document in the subcollection.
So the UI would show the fields as configured, and an additional section for fields in said document.
I am aware that FireCMS supports subcollections, but it looks like this feature is aimed at subcollections of variable size and generated ids.
Also, thanks for creating such an awesome tool, I was impressed by how easy it was to set up my workflow, and it does seem that I can extend the library easily.
Cheers
The text was updated successfully, but these errors were encountered: