Currently, if the model & collection reference are in different files, we'll get a compilation error.
This is a known limitation, but we are lacking a nice error message to catch this early on. At the moment, folks would have to find it the hard way, by having a compilation error in the generated code and googling why that is the case.
Related to https://github.com/firebase/flutterfire/issues/11228
Currently, if the model & collection reference are in different files, we'll get a compilation error. This is a known limitation, but we are lacking a nice error message to catch this early on. At the moment, folks would have to find it the hard way, by having a compilation error in the generated code and googling why that is the case.