You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this has ever been pondered about, but in my build system I would like to generate the remote objects at build time, and not commit them to the repository. As I am already using build_runner, it would be nice to also generate (remote) objects with build_runner. Was this ever attempted, and what challenges are there?
I was thinking about using a directory (for example remote_interface_definitions) containing symlinks to the locations of the interface definitions to be generated, and checking these into git. Is there maybe a better approach?
Any suggestions for a robust implementation are appreciated!
The text was updated successfully, but these errors were encountered:
I'm not sure if this has ever been pondered about, but in my build system I would like to generate the remote objects at build time, and not commit them to the repository. As I am already using build_runner, it would be nice to also generate (remote) objects with build_runner. Was this ever attempted, and what challenges are there?
I was thinking about using a directory (for example remote_interface_definitions) containing symlinks to the locations of the interface definitions to be generated, and checking these into git. Is there maybe a better approach?
Any suggestions for a robust implementation are appreciated!
The text was updated successfully, but these errors were encountered: