Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Check in regenerated C++ example registrants - #4004

Merged
fluttergithubbot merged 1 commit into
flutter-team-archive:masterfrom
stuartmorgan-g:regenerate-cpp-registrants
Jun 2, 2021
Merged

fluttergithubbot merged 1 commit into
flutter-team-archive:masterfrom
stuartmorgan-g:regenerate-cpp-registrants

Conversation

@stuartmorgan-g

Copy link
Copy Markdown
Contributor

The Flutter-generated C++ plugin registrants use a format that doesn't
match what this repo's clang-format settings wanted, so every time they
were regenerated it created a local diff that couldn't be checked in
without failing the CI format check.

The templates are now generated with a directive to disable
clang-format; this checks in that version of all of the files to avoid
the local edit problem in the future.

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 Flutter Style Guide and the C++, Objective-C, Java style guides. (Note that unlike the flutter/flutter repo, the flutter/plugins repo does use dart format. See plugin_tool format)
  • I signed the CLA.
  • The title of the PR starts with the name of the plugin 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.
  • I updated CHANGELOG.md to add a description of the change.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the 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.

The Flutter-generated C++ plugin registrants use a format that doesn't
always match what this repo's clang-format settings wanted, so every
time some of them were regenerated it created a local diff that couldn't
be checked in without failing the CI format check.

The templates are now generated with a directive to disable
clang-format; this checks in that version of all of the files to avoid
the local edit problem in the future.

@cbracken cbracken left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM stamp from a Japanese personal seal

@stuartmorgan-g stuartmorgan-g added the waiting for tree to go green (Use "autosubmit") This PR is approved and tested, but waiting for the tree to be green to land. label Jun 2, 2021
@fluttergithubbot
fluttergithubbot merged commit af4fe1b into flutter-team-archive:master Jun 2, 2021
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Jun 3, 2021
fotiDim pushed a commit to fotiDim/plugins that referenced this pull request Sep 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes p: path_provider p: shared_preferences p: url_launcher platform-linux platform-windows waiting for tree to go green (Use "autosubmit") This PR is approved and tested, but waiting for the tree to be green to land.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants