Skip to content

Fix typos #333

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 27, 2020
Merged

Fix typos #333

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ The 3.0 version of the bundle uses the newest version (2.x) of the underlying Se

The Sentry 2.0 SDK uses the Unified API, hence it uses the concept of `Scope`s to hold information about the current
state of the app, and attach it to any event that is reported. This bundle has three listeners (`RequestListener`,
`SubRequestListener` and `ConsoleListener`) that adds some easy default information. Since 3.5, a fourth listener has been added to handle the case of Messanger Workers: `MessengerListener`.
`SubRequestListener` and `ConsoleListener`) that adds some easy default information. Since 3.5, a fourth listener has been added to handle the case of Messenger Workers: `MessengerListener`.

Those listeners normally are executed with a priority of `1` to allow easier customization with custom listener, that by
default run with a lower priority of `0`.
Expand Down
4 changes: 2 additions & 2 deletions UPGRADE-3.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ changed:
* All services are now private; declare public aliases to access them if needed; you can still use the Sentry SDK global
functions if you want just to capture messages manually without injecting Sentry services in your code
* All services uses the full qualified name of their interfaces to name them
* The `ExceptionListener` has been splitted and renamed: we now have a simpler `ErrorListener`, and three other listeners
* The `ExceptionListener` has been split and renamed: we now have a simpler `ErrorListener`, and three other listeners
dedicated to enriching events of data (`RequestListener`, `SubRequestListener` and `ConsoleListener`)
* The listeners are now `final`; append your own listeners to override their behavior
* The `SentrySymfonyEvents::PRE_CAPTURE` and `SentrySymfonyEvents::SET_USER_CONTEXT` events are dropped; if you want to inject data into your events, write your own listener in a similar fashion to `RequestListener`, using the `Hub` and the `Scope` to handle how and when the new information is attached to events
Expand All @@ -53,7 +53,7 @@ This is a brief description of the services registered by this bundle:
* `Sentry\State\HubInterface`: this is the central root of the SDK; it's the `Hub` that the bundle will instantiate at
startup, and the current one too if you do not change it
* `Sentry\ClientInterface`: this is the proper client; compared to the 1.x SDK version it's a lot more slimmed down,
since a lot of the stuff has been splitted in separated components, so you probably will not interact with it as much as
since a lot of the stuff has been split in separated components, so you probably will not interact with it as much as
in the past. You also have to remind you that the client is bound to the `Hub`, and has to be changed there if you want
to use a different one automatically in error reporting
* `Sentry\ClientBuilderInterface`: this is the factory that builds the client; you can call its methods to change all
Expand Down