Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pigeon] Separates message call code generation into separate methods in the DartGenerator #5859

Merged
merged 3 commits into from
Jan 17, 2024

Conversation

bparrishMines
Copy link
Contributor

@bparrishMines bparrishMines commented Jan 10, 2024

Separates message call code generation into separate methods in the DartGenerator for flutter/flutter#134777. The ProxyApi generator uses similar code to the HostApi and FlutterApi, so this makes the code reusable.

Separated from #5544

From suggestion: #5544 (comment)

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact "@test-exemption-reviewer" in the #hackers channel in Chat (don't just cc them here, they won't see it! Use Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@bparrishMines bparrishMines changed the title some quality of life improvements [pigeon] Separates message call code generation into separate methods in the DartGenerator Jan 10, 2024
Copy link
Contributor

@tarrinneal tarrinneal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just going to open this idea for discussion.

packages/pigeon/lib/dart_generator.dart Show resolved Hide resolved
packages/pigeon/lib/dart_generator.dart Show resolved Hide resolved
packages/pigeon/lib/dart_generator.dart Show resolved Hide resolved
packages/pigeon/lib/dart_generator.dart Show resolved Hide resolved
@bparrishMines bparrishMines force-pushed the pigeon_wrapper_dart_calls branch from 6af7aeb to 830de0a Compare January 11, 2024 17:35
Copy link
Contributor

@tarrinneal tarrinneal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry, thought I had already approved this!

@bparrishMines bparrishMines added the autosubmit Merge PR when tree becomes green via auto submit App label Jan 17, 2024
@auto-submit auto-submit bot merged commit a63122c into flutter:main Jan 17, 2024
80 checks passed
@bparrishMines bparrishMines deleted the pigeon_wrapper_dart_calls branch January 17, 2024 20:16
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Jan 18, 2024
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request Jan 18, 2024
flutter/packages@1a2b780...83c2c4d

2024-01-18 [email protected] [google_maps_flutter] Restore the arm64 workaround (flutter/packages#5915)
2024-01-17 [email protected] [pigeon] Separates message call code generation into separate methods in the KotlinGenerator  (flutter/packages#5891)
2024-01-17 [email protected] [webview_flutter_wkebview] Verify JavaScriptChannels have a unique name (flutter/packages#5904)
2024-01-17 [email protected] [pigeon] Separates message call code generation into separate methods in the  `DartGenerator` (flutter/packages#5859)
2024-01-17 [email protected] Roll Flutter from 8e94423 to def6af0 (23 revisions) (flutter/packages#5911)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC [email protected],[email protected] on the revert to ensure that a human
is aware of the problem.

To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
arc-yong pushed a commit to Arctuition/packages-arc that referenced this pull request Jun 14, 2024
… in the `DartGenerator` (flutter#5859)

Separates message call code generation into separate methods in the  `DartGenerator` for flutter/flutter#134777. The `ProxyApi` generator uses similar code to the `HostApi` and `FlutterApi`, so this makes the code reusable.

Separated from flutter#5544

From suggestion: flutter#5544 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autosubmit Merge PR when tree becomes green via auto submit App p: pigeon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants