Better tools for contribuiting

[feinstein]

The Flutter repo has under the flutter tool flutter update-packages so all the nested folders with pubspec.yaml would have pub get called automatically. Also flutter ide-config --overwrite would set it up for IntelliJ IDEA.

Are there any tools for this repo as well? I can't find anything in the contributing docs. How do you guys do it? What's your workflow on this?

If there are tools, then the docs should describe them. If there aren't so maybe we should make them. Anything that helps on this matter is useful for contributing, because when I pull the git commits, that's how I get my IDE:

The red folders means they are all ignored by the IDE.

If I mark them to not be ignored I get tons of errors:

[Ehesp]

This reminds me, this PR needs to be updated and merged: #2963

[feinstein]

Is it my impression or this monorepo problem could be solved with a new feature into the Dart dependecy system? Like adding a new parameter to pubspec.yaml, letting the build system know there's a dependency for development only, probably a new behavior under dev_dependencies.

I am not experienced with monorepos, otherwise I would make a suggestion under the pub repo. Your close contact with google would sure help with this.

[Salakar]

Hey @feinstein - I will be shipping a new version of melos soon, with Windows support & also improved Intellij support;

[feinstein]

I think it is, any tests you want me to run?

[Salakar]

A good test is rename this method to anything or comment it out: https://github.com/FirebaseExtended/flutterfire/blob/master/packages/firebase_core/firebase_core/lib/src/firebase.dart#L40 - Dart Analysis warnings should appear for a lot of packages that are relying on firebase_core - if it does then that means all the packages are being interlinked correctly.

Alt+Shift+F10 on IntelliJ on Windows should also bring up a run dialog with a bunch of scripts based on the ones defined in melos.yaml, could try the 'test' one:

[Salakar]

Great thanks for confirming. I just published a quick release with a temporary fix. Will look at parsing where/which output as a more robust fix later in the week, 1am here 😅

[feinstein]

Oh forgot you guys are in the UK, no problem, let me know if you want me to open an issue at the melos repo to track this.

[feinstein]

Just a FYI on the quick fix, the postboostrap option is broken.

[Salakar]

Whats the issue with the script, pathing issue? I have a change pending to exclude postX/hook scripts from showing also.

[feinstein]

Yeah I think it's the path.

[Salakar]

Oh, ye I see the issue here, this is 'fixed' and it's no longer being generated anymore but the runConfig still exists in your .idea folder. You can go ahead and delete the file .idea/runConfigurations/melos_run_postbootstrap.xml

In a future release it will also cleanup any old/previously generated scripts that now no longer exist

[Salakar]

Can confirm by running bootstrap again after deleting the file, that file shouldn't get generated anymore

[feinstein]

Yep, I deleted it, then bootstraped again and there's no postboostrap option anymore.

[Salakar]

Forgot to mention, I pushed up a new build of melos late Monday; you should be seeing a whole lot more run configs, you can start typing when that dialog is up to easily filter, e.g. 'admob'. I've been using Android Studio now as my default editor for FlutterFire since Monday and everything seems to be ok.

[feinstein]

I really liked this!

PS: The postbootstrap still has an error on this version.