-
Notifications
You must be signed in to change notification settings - Fork 6k
Prevent solo: true
from being committed
#51712
Conversation
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!
…145928) flutter/engine@f71e5ad...a396dc1 2024-03-28 jacksongardner@google.com [skwasm] Use text position affinity when calculating word boundaries. (flutter/engine#51753) 2024-03-28 mdebbar@google.com Prevent `solo: true` from being committed (flutter/engine#51712) 2024-03-28 skia-flutter-autoroll@skia.org Manual roll Dart SDK from 291217c1d399 to bb65648e20e2 (3 revisions) (flutter/engine#51755) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll Please CC jacksongardner@google.com,rmistry@google.com,zra@google.com 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
cc @matanlurey The This change here is negating the stated goal of #50575: Deprecations in the Dart SDK (or any other external package) will now break the tree again if the deprecated properties are used in |
I don't think this change should have landed, that is, I don't think the web team unilaterally should be deciding to turn on lints we've decided not to have on as part of team-wide policy, and I'd like to consider reverting this PR. Fwiw I did work on |
This reverts commit 4e6692c.
Reverts #51712 Reason for revert: As discussed in flutter/flutter#143312, and in https://discord.com/channels/608014603317936148/1224499330824802375. I apologize if this seems hasty and not fully justified, but it is important that the engine repo follows policies like this to make it easier for our various teams to work together.
At some point, we inherited a change from the repo-level
analysis_options.yaml
that allowed deprecated members to be used. We rely on that analyzer error to preventsolo: true
from being committed in our tests (example of one that slipped recently).This PR overrides the
deprecated_member_use
error to enable it inside the web engine.