docs(flutter_weather): update tutorial #2519

jonathankao97 · 2021-06-07T16:33:33Z

Status

in development

Breaking Changes

no

Description

update flutter weather tutorial (closes #2357)

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

docs/flutterweathertutorial.md

felangel · 2021-06-07T19:20:09Z

docs/flutterweathertutorial.md

+    |-- test/
+```
+
+Next, we will be use the same packages as in the `meta_weather_api` package. In addition, we will also use the `meta_weather_api` package which we just created. Update your `pubspec.yaml` to look like the following and run `flutter packages get`


Suggested change

Next, we will be use the same packages as in the `meta_weather_api` package. In addition, we will also use the `meta_weather_api` package which we just created. Update your `pubspec.yaml` to look like the following and run `flutter packages get`

Next, we will be use the same packages as in the `meta_weather_api` package. In addition, we will also use the `meta_weather_api` package which we just created. Update your `pubspec.yaml` to look like the following and run `flutter pub get`

scarletteliza · 2021-06-07T21:17:30Z

docs/flutterweathertutorial.md


-?> **Note:** We are going to add some assets (icons for weather types) in our app, so we need to include the assets folder in the pubspec.yaml. Please go ahead and create an _assets_ folder in the root of the project.


Can we add this note back in?

docs/flutterweathertutorial.md

scarletteliza · 2021-06-07T21:44:23Z

docs/flutterweathertutorial.md

+
+### Theme Cubits
+
+Next, let's put together the HydratedCubit we will use to keep track of the theme of our app. The goal is to have the theme changed based on the current weather information.


Suggested change

Next, let's put together the HydratedCubit we will use to keep track of the theme of our app. The goal is to have the theme changed based on the current weather information.

Next, let's put together the HydratedCubit we will use to keep track of the theme of our app. The goal is to have the theme change based on the current weather information.

scarletteliza · 2021-06-07T21:44:49Z

docs/flutterweathertutorial.md

+        |-- theme_cubit.dart
+```
+
+We will expose an `updateTheme(Weather? weather)` method, which will update the theme cubit depending on the weather condition


Suggested change

We will expose an `updateTheme(Weather? weather)` method, which will update the theme cubit depending on the weather condition

We will expose an `updateTheme(Weather? weather)` method, which will update the Theme Cubit depending on the weather condition

scarletteliza · 2021-06-07T21:45:24Z

docs/flutterweathertutorial.md

+- If our weather states return correct `WeatherStatusX` values. [Here](https://github.com/felangel/bloc/blob/master/examples/flutter_weather/test/weather/cubit/weather_state_test.dart) is a completed test file
+- If our HydratedCubits respond to events properly and is able to convert fromJson and toJson
+
+In addition to using `Mocktail` for mocking and the standard testing library, it is also reccomended to use [bloc_test](https://pub.dev/packages/bloc_test) library. `bloc_test` allows us to easily prepare our blocs for testing, handle state changes, and check results.


Suggested change

In addition to using `Mocktail` for mocking and the standard testing library, it is also reccomended to use [bloc_test](https://pub.dev/packages/bloc_test) library. `bloc_test` allows us to easily prepare our blocs for testing, handle state changes, and check results.

In addition to using `Mocktail` for mocking and the standard testing library, it is also reccomended to use the [bloc_test](https://pub.dev/packages/bloc_test) library. `bloc_test` allows us to easily prepare our blocs for testing, handle state changes, and check results.

scarletteliza · 2021-06-07T21:46:03Z

docs/flutterweathertutorial.md

+
+### Weather Page
+
+With the core logic of our app put together, it's time to put together the UI! We will start with the weather page which uses `dependency injection` in order to provide cubits to widgets. This is accomplished using `BlocProvider` and `BlocConsumer`. These objects essentially inject our Cubits whenever widgets are (re)rendered.


Suggested change

With the core logic of our app put together, it's time to put together the UI! We will start with the weather page which uses `dependency injection` in order to provide cubits to widgets. This is accomplished using `BlocProvider` and `BlocConsumer`. These objects essentially inject our Cubits whenever widgets are (re)rendered.

With the core logic of our app put together, it's time to put together the UI! We will start with the weather page which uses `dependency injection` in order to provide cubits to widgets. This is accomplished using `BlocProvider` and `BlocConsumer`. These objects inject our Cubits whenever widgets are (re)rendered.

scarletteliza · 2021-06-07T21:46:17Z

docs/flutterweathertutorial.md

+}
+```
+
+This page depends on `SettingsPage, SearchPage` widgets, which we will create next


Suggested change

This page depends on `SettingsPage, SearchPage` widgets, which we will create next

This page depends on `SettingsPage, SearchPage` widgets, which we will create next.

scarletteliza · 2021-06-07T21:48:55Z

docs/flutterweathertutorial.md

+
+## Presentation Layer: Individual Weather Widgets
+
+We will next create the UI for our app. Each individual widget corresponds to a particular state our Cubits can be in.


Suggested change

We will next create the UI for our app. Each individual widget corresponds to a particular state our Cubits can be in.

Now we will create the UI for our app. Each individual widget corresponds to a particular state that our Cubits can be in.

scarletteliza · 2021-06-07T21:49:39Z

docs/flutterweathertutorial.md

+
+### WeatherPopulated
+
+Next, lets create the UI for when a city has actually been queried for.


Suggested change

Next, lets create the UI for when a city has actually been queried for.

Next, let's create the UI for when we query a city.

scarletteliza · 2021-06-07T21:49:53Z

docs/flutterweathertutorial.md

+
+## Presentation Layer: Views
+
+Let's glue the rest of our app together!


Suggested change

Let's glue the rest of our app together!

Let's put the rest of our app together!

scarletteliza · 2021-06-07T21:50:48Z

docs/flutterweathertutorial.md

+
+## Testing Our Widgets and Views
+
+In order to feel comfortable about our testing coverage, we should also test the widgets and view pages we have created. Again, we also reccomend using the `bloc_test` library for this. 


Suggested change

In order to feel comfortable about our testing coverage, we should also test the widgets and view pages we have created. Again, we also reccomend using the `bloc_test` library for this.

In order to feel confident about our testing coverage, we should also test the widgets and view pages we have created. Again, we recommend using the `bloc_test` library for this.

scarletteliza · 2021-06-07T21:51:13Z

docs/flutterweathertutorial.md

+
+[Here](https://github.com/felangel/bloc/tree/master/examples/flutter_weather/test) is an example test suite which includes widget tests, cubit tests, and view tests.
+
+## Putting it all together. Visually testing functionality


Suggested change

## Putting it all together. Visually testing functionality

## Putting it all together!

docs/flutterweathertutorial.md

scarletteliza · 2021-06-07T21:52:59Z

docs/flutterweathertutorial.md


-[weather.dart](_snippets/flutter_weather_tutorial/settings_button.dart.md ':include')
+The completed file, put together, looks like this


Suggested change

The completed file, put together, looks like this

Put together, the completed file should look like this:

scarletteliza · 2021-06-07T21:53:32Z

docs/flutterweathertutorial.md

+
+### Unit Testing our Data Layer Models
+
+First, let's unit test our data models, `location` and `weather`. We should focus on insuring that they can represent our data, translate from and to JSON form, and handle edge cases.


Suggested change

First, let's unit test our data models, `location` and `weather`. We should focus on insuring that they can represent our data, translate from and to JSON form, and handle edge cases.

First, let's unit test our data models, `location` and `weather`. We should focus on ensuring that they can represent our data, translate from and to JSON, and handle edge cases.

scarletteliza · 2021-06-07T21:53:45Z

docs/flutterweathertutorial.md

+
+First, let's unit test our data models, `location` and `weather`. We should focus on insuring that they can represent our data, translate from and to JSON form, and handle edge cases.
+
+First, add the Dart testing library to our `pubspec.yaml` and run `flutter pub get`.


Suggested change

First, add the Dart testing library to our `pubspec.yaml` and run `flutter pub get`.

Add the Dart testing library to our `pubspec.yaml` and run `flutter pub get`.

scarletteliza · 2021-06-07T21:55:54Z

docs/flutterweathertutorial.md

+
+## Repository Layer
+
+The goal of our repository layer is to create a wrapper for our data layer, and facilitate communication with the Bloc layer. In doing this, the rest of our code base depends only on functions exposed by our repository layer, instead of specific data provider implementations. This makes it easier for data providers to be switched out in the long run, and even converted into Flutter plugins/packages.


Suggested change

The goal of our repository layer is to create a wrapper for our data layer, and facilitate communication with the Bloc layer. In doing this, the rest of our code base depends only on functions exposed by our repository layer, instead of specific data provider implementations. This makes it easier for data providers to be switched out in the long run, and even converted into Flutter plugins/packages.

The goal of our repository layer is to create a wrapper for our data layer and facilitate communication with the Bloc layer. In doing this, the rest of our code base depends only on functions exposed by our repository layer, instead of specific data provider implementations. This makes it easier to switch out data providers later, or even convert them into individual Flutter plugins/packages.

scarletteliza · 2021-06-07T21:56:58Z

docs/flutterweathertutorial.md

+
+### Creating Our Weather Repository Models
+
+Update your directory structure to look like this. We will be creating a new `weather.dart` models file to contain only data we want to store, and another `models.dart` barrel file.


Suggested change

Update your directory structure to look like this. We will be creating a new `weather.dart` models file to contain only data we want to store, and another `models.dart` barrel file.

Update your directory structure to look like the below. We will create a new `weather.dart` models file to contain only data we want to store, and another `models.dart` barrel file.

scarletteliza · 2021-06-07T21:57:18Z

docs/flutterweathertutorial.md

+export 'weather.dart';
+```
+
+As we did in the previous section, run the following command to use `build_runner` to create our auto-generated models and factory methods.


Suggested change

As we did in the previous section, run the following command to use `build_runner` to create our auto-generated models and factory methods.

As we did in the previous step, run the following command to use `build_runner` to create our auto-generated models and factory methods.

scarletteliza · 2021-06-07T21:58:04Z

docs/flutterweathertutorial.md

+}
+```
+
+Lastly, update the barrel file we created previously and we are done. 


Suggested change

Lastly, update the barrel file we created previously and we are done.

Lastly, update the barrel file we created previously, and we are done with this step!

scarletteliza · 2021-06-07T21:58:26Z

docs/flutterweathertutorial.md

+
+### Testing Our Weather Repository
+
+To test our Weather Repository, we will use the [Mocktail](https://github.com/felangel/mocktail) library. Using this library, we will create mocks and insure that our weather repository's `getWeather` method works as it should. This includes testing when the API client fails, and making sure the `Weather` object returned is correct when the API call is successful.


Suggested change

To test our Weather Repository, we will use the [Mocktail](https://github.com/felangel/mocktail) library. Using this library, we will create mocks and insure that our weather repository's `getWeather` method works as it should. This includes testing when the API client fails, and making sure the `Weather` object returned is correct when the API call is successful.

To test our Weather Repository, we will use the [Mocktail](https://github.com/felangel/mocktail) library. Using this library, we will create mocks and insure that our weather repository's `getWeather` method works as it should. This includes testing when the API client fails, and making sure the returned `Weather` object is correct when the API call is successful.

scarletteliza · 2021-06-07T21:59:07Z

docs/flutterweathertutorial.md

+
+## Business Logic Layer: Weather Model
+
+In this section, we're going to implement our third weather model - this time for the weather feature of our main app. Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app, and in this weather model, we will bake temperature settings into the weather model.


Suggested change

In this section, we're going to implement our third weather model - this time for the weather feature of our main app. Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app, and in this weather model, we will bake temperature settings into the weather model.

In this section, we're going to implement our third weather model - this time for the weather feature of our main app. The goal of this model is to keep track of weather data displayed by our app and app settings.

Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app. In this weather model, we will bake temperature settings into the weather model.

scarletteliza · 2021-06-07T21:59:21Z

docs/flutterweathertutorial.md

+
+In this section, we're going to implement our third weather model - this time for the weather feature of our main app. Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app, and in this weather model, we will bake temperature settings into the weather model.
+
+Before we get started, lets update our project level dependencies to import the packages we've created and also the serialization/deserialization dependencies.


Suggested change

Before we get started, lets update our project level dependencies to import the packages we've created and also the serialization/deserialization dependencies.

Before we get started, let's update our project-level dependencies to import the packages we've created and the serialization/deserialization dependencies.

scarletteliza · 2021-06-07T21:59:51Z

docs/flutterweathertutorial.md

+    - assets/
+```
+
+We will be working in the `weather` features app, in our main project library.


Suggested change

We will be working in the `weather` features app, in our main project library.

We will be working inside the `weather` features app, in our main project library.

scarletteliza · 2021-06-07T22:00:26Z

docs/flutterweathertutorial.md

+      |-- weather.dart
+```
+
+The goal of our weather model is to keep track of weather data displayed by our app and also to keep track of settings. To keep track of settings (celsius, farenheit), create the temperature model in `weather`


Suggested change

The goal of our weather model is to keep track of weather data displayed by our app and also to keep track of settings. To keep track of settings (celsius, farenheit), create the temperature model in `weather`

To keep track of settings (celsius, farenheit), create the temperature model in `weather`

Moved the first sentence up to the top of this section

scarletteliza · 2021-06-07T22:02:02Z

docs/flutterweathertutorial.md

+}
+```
+
+Lastly, to wrap this section up, run `build_runner` to create the auto generated file and methods, and also export our models in the barrel file


Suggested change

Lastly, to wrap this section up, run `build_runner` to create the auto generated file and methods, and also export our models in the barrel file

To wrap this section up, run `build_runner` to create the auto generated file and methods, then export our models in the barrel file.

scarletteliza · 2021-06-07T22:03:04Z

docs/flutterweathertutorial.md

+
+## Business Logic Layer: Weather and Theme Cubits
+
+In this tutorial, we will use HydratedCubits for our Bloc layer. HydratedCubits are essentially Cubits that can persist state across sessions when used in conjunction with HydratedStorage. In short, our HydratedCubits will keep track of state and expose methods which can be used to mutate state.


Suggested change

In this tutorial, we will use HydratedCubits for our Bloc layer. HydratedCubits are essentially Cubits that can persist state across sessions when used in conjunction with HydratedStorage. In short, our HydratedCubits will keep track of state and expose methods which can be used to mutate state.

Now, we will use HydratedCubits for our Bloc layer to allow for theming. HydratedCubits are Cubits that can persist state across sessions when used in conjunction with HydratedStorage. In short, our HydratedCubits will keep track of state and expose methods which can be used to mutate state.

scarletteliza · 2021-06-07T22:03:50Z

docs/flutterweathertutorial.md

+}
+```
+
+We will also need to keep track of what units (farenheit or celsius) our app is in. 


Suggested change

We will also need to keep track of what units (farenheit or celsius) our app is in.

We will also need to keep track of what units (Fahrenheit or Celsius) our app is using.

scarletteliza · 2021-06-07T22:04:06Z

docs/flutterweathertutorial.md

+
+### Weather Cubits
+
+Finally! It's time to put together our Weather Cubit. Our Weather Cubit will expose the following methods:


Suggested change

Finally! It's time to put together our Weather Cubit. Our Weather Cubit will expose the following methods:

It's time to put together our Weather Cubit which will expose the following methods:

felangel

LGTM 🚀 🎉

jonathankao97 added 2 commits June 4, 2021 11:36

flutter weather tutorial first draft

1a11b2b

update flutter weather tutorial typos

6fe1205

jonathankao97 requested a review from felangel as a code owner June 7, 2021 16:33

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

felangel reviewed Jun 7, 2021

View reviewed changes

scarletteliza reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

scarletteliza reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

scarletteliza reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

scarletteliza reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Show resolved Hide resolved

scarletteliza reviewed Jun 7, 2021

View reviewed changes

docs/flutterweathertutorial.md Outdated Show resolved Hide resolved

scarletteliza reviewed Jun 7, 2021

View reviewed changes

felangel assigned jonathankao97 Jun 7, 2021

felangel added the documentation Documentation requested label Jun 7, 2021

felangel added this to In progress in Upgrade Documentation via automation Jun 7, 2021

felangel added 10 commits June 11, 2021 00:09

docs(flutter_weather): tutorial updates

4071093

docs: more weather tutorial updates

5ccf208

Merge branch 'master' into flutter_weather

60f5a48

docs: consolidate complete code snippets

4e1229c

snippets cleanup

4bd6e03

update other tutorials

0172086

minor updates

3187637

Merge branch 'master' into flutter_weather

5e8407b

docs: minor edits

6c3e103

docs: minor updates to sidebar

ff5f3ed

felangel approved these changes Jun 17, 2021

View reviewed changes

felangel merged commit f9a4de9 into felangel:master Jun 17, 2021

Upgrade Documentation automation moved this from In progress to Done Jun 17, 2021

Nomeleel pushed a commit to Nomeleel/bloc that referenced this pull request Jul 23, 2021

docs(flutter_weather): update tutorial (felangel#2519)

181fb1d

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs(flutter_weather): update tutorial #2519

docs(flutter_weather): update tutorial #2519

jonathankao97 commented Jun 7, 2021 •

edited by felangel

felangel Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021 •

edited

scarletteliza Jun 7, 2021 •

edited

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021 •

edited

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021

scarletteliza Jun 7, 2021 •

edited

felangel left a comment

	Next, we will be use the same packages as in the `meta_weather_api` package. In addition, we will also use the `meta_weather_api` package which we just created. Update your `pubspec.yaml` to look like the following and run `flutter packages get`
	Next, we will be use the same packages as in the `meta_weather_api` package. In addition, we will also use the `meta_weather_api` package which we just created. Update your `pubspec.yaml` to look like the following and run `flutter pub get`


		?> Note: We are going to add some assets (icons for weather types) in our app, so we need to include the assets folder in the pubspec.yaml. Please go ahead and create an _assets_ folder in the root of the project.


		### Theme Cubits

		Next, let's put together the HydratedCubit we will use to keep track of the theme of our app. The goal is to have the theme changed based on the current weather information.

	We will expose an `updateTheme(Weather? weather)` method, which will update the theme cubit depending on the weather condition
	We will expose an `updateTheme(Weather? weather)` method, which will update the Theme Cubit depending on the weather condition

	In addition to using `Mocktail` for mocking and the standard testing library, it is also reccomended to use [bloc_test](https://pub.dev/packages/bloc_test) library. `bloc_test` allows us to easily prepare our blocs for testing, handle state changes, and check results.
	In addition to using `Mocktail` for mocking and the standard testing library, it is also reccomended to use the [bloc_test](https://pub.dev/packages/bloc_test) library. `bloc_test` allows us to easily prepare our blocs for testing, handle state changes, and check results.


		### Weather Page

		With the core logic of our app put together, it's time to put together the UI! We will start with the weather page which uses `dependency injection` in order to provide cubits to widgets. This is accomplished using `BlocProvider` and `BlocConsumer`. These objects essentially inject our Cubits whenever widgets are (re)rendered.

	This page depends on `SettingsPage, SearchPage` widgets, which we will create next
	This page depends on `SettingsPage, SearchPage` widgets, which we will create next.


		## Presentation Layer: Individual Weather Widgets

		We will next create the UI for our app. Each individual widget corresponds to a particular state our Cubits can be in.

	We will next create the UI for our app. Each individual widget corresponds to a particular state our Cubits can be in.
	Now we will create the UI for our app. Each individual widget corresponds to a particular state that our Cubits can be in.


		### WeatherPopulated

		Next, lets create the UI for when a city has actually been queried for.

	Next, lets create the UI for when a city has actually been queried for.
	Next, let's create the UI for when we query a city.


		## Presentation Layer: Views

		Let's glue the rest of our app together!

	Let's glue the rest of our app together!
	Let's put the rest of our app together!


		## Testing Our Widgets and Views

		In order to feel comfortable about our testing coverage, we should also test the widgets and view pages we have created. Again, we also reccomend using the `bloc_test` library for this.

	In order to feel comfortable about our testing coverage, we should also test the widgets and view pages we have created. Again, we also reccomend using the `bloc_test` library for this.
	In order to feel confident about our testing coverage, we should also test the widgets and view pages we have created. Again, we recommend using the `bloc_test` library for this.


		[Here](https://github.com/felangel/bloc/tree/master/examples/flutter_weather/test) is an example test suite which includes widget tests, cubit tests, and view tests.

		## Putting it all together. Visually testing functionality

	## Putting it all together. Visually testing functionality
	## Putting it all together!


		[weather.dart](_snippets/flutter_weather_tutorial/settings_button.dart.md ':include')
		The completed file, put together, looks like this

	The completed file, put together, looks like this
	Put together, the completed file should look like this:


		### Unit Testing our Data Layer Models

		First, let's unit test our data models, `location` and `weather`. We should focus on insuring that they can represent our data, translate from and to JSON form, and handle edge cases.

docs(flutter_weather): update tutorial #2519

docs(flutter_weather): update tutorial #2519

Conversation

jonathankao97 commented Jun 7, 2021 • edited by felangel

Status

Breaking Changes

Description

Type of Change

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

scarletteliza Jun 7, 2021 • edited

Choose a reason for hiding this comment

scarletteliza Jun 7, 2021 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

scarletteliza Jun 7, 2021 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

scarletteliza Jun 7, 2021 • edited

Choose a reason for hiding this comment

felangel left a comment

Choose a reason for hiding this comment

jonathankao97 commented Jun 7, 2021 •

edited by felangel

scarletteliza Jun 7, 2021 •

edited

scarletteliza Jun 7, 2021 •

edited

scarletteliza Jun 7, 2021 •

edited

scarletteliza Jun 7, 2021 •

edited


		First, let's unit test our data models, `location` and `weather`. We should focus on insuring that they can represent our data, translate from and to JSON form, and handle edge cases.

		First, add the Dart testing library to our `pubspec.yaml` and run `flutter pub get`.

	First, add the Dart testing library to our `pubspec.yaml` and run `flutter pub get`.
	Add the Dart testing library to our `pubspec.yaml` and run `flutter pub get`.


		## Repository Layer

		The goal of our repository layer is to create a wrapper for our data layer, and facilitate communication with the Bloc layer. In doing this, the rest of our code base depends only on functions exposed by our repository layer, instead of specific data provider implementations. This makes it easier for data providers to be switched out in the long run, and even converted into Flutter plugins/packages.


		### Creating Our Weather Repository Models

		Update your directory structure to look like this. We will be creating a new `weather.dart` models file to contain only data we want to store, and another `models.dart` barrel file.

	As we did in the previous section, run the following command to use `build_runner` to create our auto-generated models and factory methods.
	As we did in the previous step, run the following command to use `build_runner` to create our auto-generated models and factory methods.

	Lastly, update the barrel file we created previously and we are done.
	Lastly, update the barrel file we created previously, and we are done with this step!


		### Testing Our Weather Repository

		To test our Weather Repository, we will use the [Mocktail](https://github.com/felangel/mocktail) library. Using this library, we will create mocks and insure that our weather repository's `getWeather` method works as it should. This includes testing when the API client fails, and making sure the `Weather` object returned is correct when the API call is successful.


		## Business Logic Layer: Weather Model

		In this section, we're going to implement our third weather model - this time for the weather feature of our main app. Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app, and in this weather model, we will bake temperature settings into the weather model.

-In this section, we're going to implement our third weather model - this time for the weather feature of our main app. Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app, and in this weather model, we will bake temperature settings into the weather model.
+In this section, we're going to implement our third weather model - this time for the weather feature of our main app. The goal of this model is to keep track of weather data displayed by our app and app settings.
+Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app. In this weather model, we will bake temperature settings into the weather model.


		In this section, we're going to implement our third weather model - this time for the weather feature of our main app. Note that we haven't been implementing the exact same model each time. In the API client package, our weather model contained all the info returned by the API. In the repository client package, our weather model contained only the data we wish to display in our app, and in this weather model, we will bake temperature settings into the weather model.

		Before we get started, lets update our project level dependencies to import the packages we've created and also the serialization/deserialization dependencies.