-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto on session tracking #517
base: master
Are you sure you want to change the base?
Changes from 12 commits
f9d9b38
4ec3855
7168505
488c4fe
3c71e1e
b8b2020
93b2d4c
b3aa1b0
45b401a
fa0bcc8
1a4f433
bcd2058
e2b6269
8b8b3cc
bde1c08
ab3cc78
7acfea6
4e8b739
6fa5b16
660abaa
bccd728
9d466c0
27143e8
00a6a88
e2898c1
8f5ab58
c91f17d
9a7ca29
d959d3e
19ab537
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,27 @@ | ||
Upgrading | ||
========= | ||
|
||
## 3.x to 4.x | ||
|
||
#### Setting Endpoints | ||
|
||
The way endpoints will be configured has been change slightly, in order to make sure all of your requests get send to the correct place. You'll no longer be able to pass the `endpoint` parameter to your `Bugsnag\Client::make` calls, and should instead use the [`setEndpoints` configuration option](https://docs.bugsnag.com/platforms/php/other/configuration-options/#endpoints). If you've previously used the `BUGSNAG_ENDPOINT` environment variable, it's now been renamed to `BUGSNAG_NOTIFY_ENDPOINT`, and will only work in conjunction with the `BUGSNAG_SESSION_ENDPOINT` environment variable, to make sure that both endpoints are being used correctly. | ||
Cawllec marked this conversation as resolved.
Show resolved
Hide resolved
Cawllec marked this conversation as resolved.
Show resolved
Hide resolved
Cawllec marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
#### Configuring the GuzzleHttp Client | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this change required for always on session tracking? |
||
|
||
If you've previously customized the GuzzleHttp Client we use to deliver notifications, you'll no longer be able to pass it in to a `new Bugsnag\Client` call. Instead you'll need to add it to Bugsnag using the [`setGuzzleClient` configuration option.](https://docs.bugsnag.com/platforms/php/other/configuration-options/#guzzle-client) | ||
|
||
#### Deprecation | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this change required for always on session tracking? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This isn't, but should be removed if this is a major release. I've removed it as it'll be a part of a release PR instead. |
||
|
||
The `deploy` method has been removed, so in order to report a new version build to bugsnag you should use the `build` method, [as described here.](https://docs.bugsnag.com/platforms/php/other/#tracking-releases) | ||
|
||
## 2.x to 3.x | ||
|
||
*Our PHP library has gone through some major improvements, and there are some small changes you'll need to make to get onto the new version.* | ||
|
||
#### PHP 5.5+ | ||
|
||
We now require PHP 5.5 or higher. If you're using an older version of PHP, you can still use v2. We will containue to maintain v2 along side v3. For more information, see the [legacy PHP integration guide](https://docs.bugsnag.com/platforms/php/other/legacy/). | ||
We now require PHP 5.5 or higher. If you're using an older version of PHP, you can still use v2. We will continue to maintain v2 along side v3. For more information, see the [legacy PHP integration guide](https://docs.bugsnag.com/platforms/php/other/legacy/). | ||
|
||
#### Namespaces | ||
|
||
|
@@ -22,7 +35,7 @@ The method for setting the application type (`setType`) has also been removed in | |
|
||
#### Configuration | ||
|
||
We've changed how our configuration system works. You can now build up our config object in a similar way to how you configured the client in v2, and then pass that as the first paramater when you construct the client object. In addition, we've removed some configuration options in favour of using our new notification pipeline system. Now you can register multiple callbacks to have maximum flexibility. We've also switched to using [Guzzle](http://guzzlephp.org), so you can change the base URI and proxy details by directly interacting with guzzle. For more information, see the [advanced configuration guide](https://docs.bugsnag.com/platforms/php/other/advanced-client-configuration). | ||
We've changed how our configuration system works. You can now build up our config object in a similar way to how you configured the client in v2, and then pass that as the first parameter when you construct the client object. In addition, we've removed some configuration options in favour of using our new notification pipeline system. Now you can register multiple callbacks to have maximum flexibility. We've also switched to using [Guzzle](http://guzzlephp.org), so you can change the base URI and proxy details by directly interacting with guzzle. For more information, see the [advanced configuration guide](https://docs.bugsnag.com/platforms/php/other/advanced-client-configuration). | ||
|
||
#### Customizing handled errors | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than bumping the major version why not support backwards compat?