refactor(just): slim down mobile-dev to just run Flutter#801
Merged
Conversation
mobile-dev was bundling migrations, Docker service startup, and relay compilation (with a 90-second polling loop) alongside the Flutter run. The desktop dev recipe doesn't do this — it expects the relay to already be running via `just relay`. Mobile should follow the same pattern.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
just mobile-devwas bundling infra concerns — running migrations, starting Docker services, and compiling and polling for the relay — alongside just launching Flutter. This made it slow and inconsistent with how desktop development works.The desktop
just devrecipe doesn't touch the relay at all; it expects the developer to runjust relayseparately. Mobile should follow the same pattern. The relay startup alone could take 30–90 seconds ofcargo runcompilation time, which isn't the mobile developer's problem to manage on everyflutter run.just _ensure-migrationscall frommobile-devcargo run, 90s polling loop, trap)just relayalready covers all the removed functionality (it depends on_ensure-migrations→_ensure-services)