Skip to content

Commit

Permalink
Added changelog and readme file
Browse files Browse the repository at this point in the history
  • Loading branch information
gmponos committed Dec 13, 2018
1 parent 6c0285d commit 694eba2
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 7 deletions.
18 changes: 11 additions & 7 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,22 +2,26 @@

All Notable changes to `gmponos/guzzle_logger` will be documented in this file

## [UNRELEASED]
## 0.8.0 - 2018-12-13

### BREAKING CHANGES
### Changes

- Set as the default strategy in all handlers the `FixedStrategy`

**BREAKING CHANGES**

- `LogLevelStrategy` class is removed and it has been separated to smaller classes.
Check the added classes below.
Check the `added` section below.
- Changed the namespaces completely. The new Namespace is `GuzzleLogMiddleware` instead of `Gmponos\GuzzleLogger`.
Check the README file for instructions.
Check the README file for instructions.
- Changed the signature of function `HandlerInterface::log`.
- Changed `ArrayHandler` to `MultiRecordArrayHandler`

### Added
- `FixedStrategy` a strategy that you are able to set one level for all your logs.
- `ThresholdLevelStrategy` a strategy that works with thresholds depending on the status code.
- `StatusCodeStrategy` a strategy that you are able to set a specific log level per status code.

### Changed
- Set as the default strategy in all handlers the `FixedStrategy`

## 0.7.0 - 2018-11-15

### Changed
Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ The middleware is functional with Guzzle 6.
we are still on 0.x.x version. If you use the package for a project that is in production please lock this package in your composer
to a specific version like `^0.3.0`.

**Note** That hopefully 0.8.0 version will be the last unstable.

## Install

Via Composer
Expand Down

0 comments on commit 694eba2

Please sign in to comment.