refactor(weather_example): use named extension

[gcugnet]

Name the double extension to make it available through imports in other files (i.e. in weather_cubit_test.dart).

Status

READY

Breaking Changes

NO

Description

I’m following the flutter_weather example, and I encountered an error in the weather_cubit_test.dart file:

The method 'toFahrenheit' isn't defined for the type 'double'.
Try correcting the name to the name of an existing method, or defining a method named 'toFahrenheit'.dart[undefined_method](https://dart.dev/diagnostics/undefined_method)
Type: InvalidType

However exports and imports are correct (I double-checked them).

Just naming the extension fixes this error.

EDIT: I realized a bit later that the extension was added again in the test file. So the current code is fully functional and my PR is less necessary.

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• [] 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[gcugnet]

Sorry, I haven’t seen the extension declaration on test file.

extension on double {
  double toFahrenheit() => (this * 9 / 5) + 32;
  double toCelsius() => (this - 32) * 5 / 9;
}

I’ll remove it in a new commit, to make it cleaner.
Don’t know if my PR really enhance the example code, and it’s not a fix anymore but a refactor.

[felangel]

LGTM thanks for the cleanup! 💙