Closed VolodymyrReient closed 2 years ago
Based on your suggestion, this doesn't know seem to be under our control. The Firebase team allows for one collection at a time to be monitored per extension. You can install the extension multiple times to listen for each sub collection. You might want to chat with the Firebase team on this use case to see what they say.
Based on your suggestion, this doesn't know seem to be under our control. The Firebase team allows for one collection at a time to be monitored per extension. You can install the extension multiple times to listen for each sub collection. You might want to chat with the Firebase team on this use case to see what they say.
Maybe add ability to configure more that one Collection Path at the same time (e.x create second input for Collection Path) - this field
hey @VolodymyrReient adding additional inputs would not really do anything if the provision scripts are not set up to recognize the additional inputs. The provisioning scripts are managed by the Firebase team.
I have a collection "announcements". This collection has a six subcollections. An example of collection - screen. I can index only one subcollection (e.x path -
announcements/announcements/list
)I think it's good to be able to choose all subcollections into a single search index: e.x
announcements/*/list
( symbol*
just for example) When i set collection path likeannouncements/*/list
algolia index all subcollectionsProbably this link will be usefull link