Lukas Klingsbo
Lukas Klingsbo
@albinpk currently it would be to put the code inside of a subdirectory and let it have its own pubspec.
@albinpk I don't think that would work, I think the pub workspace has to be defined in the root. And we also don't want to have a different structure than...
We just got rid of the `melos.yaml` file because people didn't want to have extra files in their repository, so it wouldn't be an option to have the user creating...
The solution for this is now released in v7.1.0 https://melos.invertase.dev/configuration/overview#userootaspackage
Can you elaborate what you mean with textureId here, and also how you envision that platform views would work in Flame 3D?
Sounds good, I'll assign you to the issue! Two initial notes about the implementation: - The `instances` argument needs a better name. - The culling feels too specific to be...
Makes sense, would you be interested in working on that issue?
> Should propagate first and then run pub get. Unfortunately it can't, because the initial `pub get` gets the Melos version that is going to be used for the execution...
If the [cli_launcher](https://github.com/blaugold/cli_launcher) package updated so that it could take in flags for `dart pub get` I think we could support this properly, this is where it is used: https://github.com/blaugold/cli_launcher/blob/main/lib/cli_launcher.dart#L191-L205.
We can now go ahead and do this since https://github.com/blaugold/cli_launcher/issues/10 is released. I'm quite busy with organizing Flutter & Friends at the moment, is anyone else keen on putting up...