So there's some validation in place to make sure we're receiving an array of UUIDs.
Problem is, however, precisely when I'm not receiving an array of UUIDs.
This validator is originally based on WTForms Number Range validator.
If your Firebase client app communicates with a custom backend server, you might need to identify the currently signed-in user on that server.
You can re-use that ID token to identify the user or device on your custom backend server.
To retrieve the ID token from the client, make sure the user is signed in and then get the ID token from the signed-in user: Once you have an ID token, you can send that JWT to your backend and validate it using the Firebase Admin SDK, or using a third-party JWT library if your server is written in a language which Firebase does not natively support.
Suppose, we have a model called The problem here is that accepts_nested_attributes_for call destroy for child objects AFTER validation of the parent object. Of course, later, when the user will try to edit a company, he/she will get an error - “Company should have at least one office.”.
), and it actually works, but again, it does not take into account the fact that some of the records may be marked for destruction. To sort out the problem, we need to understand what # accepts_nested_attributes_for generates for us this method def offices_attributes=(attributes) # @note the name of the method to call may vary depending on the type of association # @see https://github.com/rails/rails/blob/master/activerecord/lib/active_record/nested_attributes.rb#L285 assign_nested_attributes_for_collection_association(:offices, attributes, mass_assignment_options) end def assign_nested_attributes_for_collection_association ... call_reject_if(association_name, attributes) # if the record passed # update a record with the attributes or marks it for destruction assign_to_or_mark_for_destruction(existing_record, attributes, options[:allow_destroy], assignment_opts) end ...
The ID token verification methods included in the Firebase Admin SDKs are meant to verify ID tokens that come from the client SDKs, not the custom tokens that you create with the Admin SDKs. To verify ID tokens with the Firebase Admin SDK, you must have a service account.The countries are Bosnia and Herzegovina, Brazil, Bulgari, Chile, China, Croatia, Czech, Denmark, Estonia, Finland, Iceland, Ireland, Latvia, Lithuania, Macedonia, Montenegro, Netherlands, Poland, Romania, San Marino, Serbia, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Thailand.So I have this entity above, which has a matching Symfony form and it's all tied up nicely by a controller.Follow the Admin SDK setup instructions for more information on how to initialize the Admin SDK with a service account.When a user or device successfully signs in, Firebase creates a corresponding ID token that uniquely identifies them and grants them access to several resources, such as Firebase Realtime Database and Cloud Storage.