-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Discontinue the deprecated screaming snake case constants from dart:io #34218
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
Comments
Dart three-point-ohhhhhhh |
@mit-mit - Have we decided on how we will collect and track these decisions? In this case we've discussed even removing them before Dart 3.0 |
Proof-of-concept: https://dart-review.googlesource.com/c/sdk/+/219791 |
Does |
Most of them. There are a couple that are not covered because |
@natebosch the issue you linked to looks resolved, so does |
No. https://dart-review.googlesource.com/c/sdk/+/214068 attempts to use these fixes and the test failures show that there is still a problem. I forwarded you an internal thread with some more detail. |
Updating title: Analysis of both internal and external code shows very little use of these long discontinued SCREAMING CASE APIs, so we're going ahead with the removal. |
Bug: #34218 Change-Id: I4215c0a2212d5c15972d9ffe4075c89d27c9081e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/235701 Reviewed-by: Daco Harkes <[email protected]> Reviewed-by: William Hesse <[email protected]> Commit-Queue: Paul Berry <[email protected]>
HOORAY! FANTASTIC! I CAN TURN MY CAPS LOCK KEY OFF NOW! 🥇 |
There are a few more to remove in |
Forking the conversation from #31813
We have added new lowercase constants and migrated all internal code, and external code authored by the Dart team to use it. We need to determine whether we want to remove the deprecated constants for Dart 3.0 (then figure out how to keep track of these things so we don't miss them for that release)
My vote would be to remove them. They'll be deprecated for a long time by that point and the migration is really easy to do.
The text was updated successfully, but these errors were encountered: