|
1 | 1 | # API Response Builder for Laravel 5 #
|
2 | 2 |
|
3 |
| -`ResponseBuilder` is Laravel5's helper designed to simplify building |
4 |
| -nice, normalized and easy to consume REST API responses. |
| 3 | + `ResponseBuilder` follows [Semantic Versioning](http://semver.org/). |
5 | 4 |
|
6 |
| -## Preface ## |
| 5 | + You need to worry about backward compatibility if you are upgrading from previous major version of the package. |
7 | 6 |
|
8 |
| - **NOTE:** You should **ONLY** worry about compatibility if you are upgrading from previous versions as you may |
9 |
| - be using APIs that changed. If you are new to the project and you just started using it, simply do not bother |
10 |
| - untill **next major update** (see [Semantic Versioning](http://semver.org/)). |
| 7 | +### v3 ### |
11 | 8 |
|
12 |
| -## Compatibility ## |
| 9 | + * `success()` now accepts (optional) `api_code` too, therefore signature of this method as well as and argument |
| 10 | + order changed. This makes it **partially** incompatible with what have been in v2, however in majority of uses |
| 11 | + this change should pose no threat at all. If you were just calling `success()` or `success($data)` (which is |
| 12 | + 99,9% of use cases) then you are all fine and no change is needed. But if you were setting own |
| 13 | + `http_code` or `lang_args` when calling `success()` then you need to update your code. |
13 | 14 |
|
14 |
| - Backward INCOMPATIBLE changes detailed. |
| 15 | +### v2 ### |
15 | 16 |
|
16 |
| -### v3.0 ### |
| 17 | + * First public release. |
17 | 18 |
|
18 |
| - * `success()` changed to allow returning custom `api_code` with response, therefore signature of this method |
19 |
| - (and argument order) is different which makes it **partially** incompatible. In majority of uses this is not |
20 |
| - a problem but if you were calling `success()` passing `http_code` or `lang_args` to it, then you need to |
21 |
| - update your code to work properly with 3.0.0. But if you were just calling `success()` or `success($data)` |
22 |
| - (which is 99,9% of use cases) then you are all fine and no change is needed. |
23 |
| - |
24 |
| -### v2.x ### |
25 |
| - |
26 |
| - * No public API changes. |
27 |
| - |
28 |
| -### v1.x ### |
| 19 | +### v1 ### |
29 | 20 |
|
30 | 21 | * Initial (internal) release
|
31 |
| - |
32 |
| -## Changelog ## |
33 |
| - |
34 |
| - See [CHANGES.md](CHANGES.md) for detailed revision history. |
0 commit comments