Custom validation logic for Firebase remote config values?

We use Firebase Remote Config

to switch functions remotely in our applications Android

and iOS

. All top-level functions (menu items of menu items) can be switched to boolean

config values .

Hence, it is possible that all functions will be random disabled

, leaving users with an empty application shell.

We could add some client-side logic to dispense with the sensible configuration of functions, but in our case there are reasons why this is not easy (each function depends on the availability of the server module).

Is there a way to specify some custom validation rules for values Firebase Remote Config

? Ideally, it would be great if they were server-side, so it was not possible to post changes that had all toggle functionality disabled in the first place.

Alternatively there could be some kind of client side validation, but it looks like it has to do with creating some kind of local cache to use as the source of truth instead of using the built in local cache + the default Remote Config (which doesn't sound like a lot).

+3


source to share


1 answer


There is currently no server side validation that you can do on the Remote Config values.



If you think such a thing would be useful, I would suggest that you fill out a feature request at https://firebase.google.com/support/contact/bugs-features/.The team reviews these requests regularly.

+1


source







All Articles