-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[various] Standardize Gradle namespace
#10084
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
[various] Standardize Gradle namespace
#10084
Conversation
Standardizes namespace on the `=` form of property assignment, and updates the existing namespace check to require that version. Also standardizes these lines on `"` rather than `'` while touching them. Part of flutter/flutter#176065
CHANGELOG/version override: this is a no-op style change, so doesn't impact clients. |
signingConfig signingConfigs.debug | ||
} | ||
} | ||
namespace 'com.example.example' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This example app had somehow ended up with two namespaces.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request standardizes the Gradle namespace
property to use the =
assignment form and double quotes across numerous build.gradle
files. It also updates the gradle-check
tool to enforce this new convention. The changes are well-executed and improve consistency. I've found one issue in the test suite where a test case is not correctly asserting a failure, which could lead to undetected regressions.
/// compatibility with apps that use AGP 8+. | ||
bool _validateNamespace(RepositoryPackage package, String gradleContents, | ||
{required bool isExample}) { | ||
// Regex to validate that either of the following namespace definitions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean to delete "of"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant to rewrite the sentence more than I did; I'm not sure what happened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
autosubmit label was removed for flutter/packages/10084, because - The status or check suite Mac_arm64 ios_platform_tests_shard_3 master has failed. Please fix the issues identified (or deflake) before re-applying this label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
namespace
namespace
Standardizes namespace on the
=
form of property assignment, and updates the existing namespace check to require that version.Also standardizes these lines on
"
rather than'
while touching them.Part of flutter/flutter#176065
Pre-Review Checklist
[shared_preferences]
pubspec.yaml
with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under1.CHANGELOG.md
to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under1.///
).Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2 ↩3