Repository navigation
test(auth,database,functions): move e2e suites into their example apps - #18541
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
dff396d to
76c3b20
Compare
76c3b20 to
4127bd3
Compare
Second wave of per-product e2e migrations on the storage template. Each product gets a path-filtered, platform-scoped workflow (a Kotlin-only change runs android only), its own emulator per job, and builds linking only its own native deps instead of the mega-app's ~26. - auth: 5 files, windows coverage preserved (it had it in the mega-app windows run); iOS stays CocoaPods because flutter_facebook_auth ^7.1.5 currently resolves to 7.1.6 which ships no Package.swift - CocoaPods is correct under either resolution; flip to SPM when the constraint moves to ^7.2.0 - database: 8 files including the conditional web_only import pair; iOS runs SPM (all deps ship Package.swift); no windows job (never had coverage, example has no windows/) - functions: 2 files; iOS runs SPM; no windows job - generator: --auth-native/--database-native/--functions-native; database needed a separate macOS bundle id (differs from iOS) - mega-app: auth + database_functions shards and matrix legs removed; only core_misc remains; tests/pubspec.yaml untouched (coexistence) - nightly + dashboard wired for the three new workflows
… SPM 7.2.0 is the first release shipping a Package.swift; with it every plugin in the example resolves under Swift Package Manager, so the iOS job moves off CocoaPods (macOS keeps it - both managers stay covered).
4127bd3 to
3dd30df
Compare
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process. Updating the
pubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?