Ryan Brown

Here's some background context on our side. We've been using various Google Cloud apis for many years. So I guess we've gotten used to thinking "Google apis return grpc errors."...

Yes. I just want to mention what has been the most confusing thing for us. When we use the classroom api, we see errors that look a lot like grpc...

Yes, those are not valid urls. I am trying to use katex from a website whose CSP policy only allows fonts hosted on one of those two domains. The first...

Sorry, let me try to explain this better. Reference fields store a Firestore reference, but also hold type information for the code generator. As far as the rules generator is...

Also I may use a repeated field instead of a map. A map is closer to how Collections work, but since it's going to be handled specially by the code...

I don't think extra_properties helps, but an option to ignore a field would.

I came up with a workaround here, although it seems pretty hacky. I wrote another code generator that wraps //firebase_rules_generator:firebase_rules_options and //firebase_rules_generator:generator. It modifies the CodeGeneratorRequest to convert from (protofire.field)...

Closure Library and MDL are both also deprecated, which this project uses for its UI components. It seems like a total re-write might be necessary.

I think the docs are supposed to be here: https://docs.google.com/document/d/1CE6wJHNfKbUPBr7-mmk_0Yo3a4TaqcTPE0OWNuQkhPs/edit#heading=h.5mcn15i0e1ch But it's still not clear how I write a foo_proto_library rule using the new toolchains.