-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
11 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,25 @@ | ||
## 1.0.0 | ||
## [1.0.1] - 19-11-2023 | ||
|
||
- fix: limit when get location in GeocodingService (thanks svoza10 for [#7](https://github.com/PackRuble/weather_pack/pull/7)) | ||
- upd: improving changelog according to some excerpts from keepachangelog.com | ||
|
||
## [1.0.0] - 28-07-2023 | ||
|
||
- bump dependencies. Now we use dart 3.0 | ||
|
||
## 0.1.0 | ||
## [0.1.0] - 28-07-2023 | ||
|
||
- fix [issue #1](https://github.com/PackRuble/weather_pack/issues/1) of hiding `parseCurrent` from public api | ||
- add assert for latitude and longitude | ||
- `WeatherService` and `GeocodingService`, and `OWMApiTest` now accept `client` as a parameter. This can be handy when testing | ||
- bump dependencies. The next release will be an upgrade to Dart 3.0 | ||
|
||
## 0.0.2 | ||
## [0.0.2] - 27-12-2022 | ||
|
||
* fix [issue #5](https://github.com/PackRuble/weather_pack/issues/5) when some boundary cases were not taken into account | ||
* add to the "example" folder console application. A detailed analysis of code writing will be provided later | ||
* add visual resources to documentation, styling of the package was adjusted, link to telegram [channel](https://t.me/+AkGV73kZi_Q1YTMy) is attached | ||
|
||
## 0.0.1 | ||
## [0.0.1] - 21-10-2022 | ||
|
||
* Initial development release. Hi pub.dev |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters