User data processor improvements #17
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a collection of patches which improve the user data processor, both in documentation and features.
The main changes other than documentation are these:
appends
option, which allows extra fields from the user to be added, even if they were not part of the user object'stoArray
return value. This is sometimes useful to include a field which is useful when debugging errors but which is not normally needed when getting data about a user, for example when sending it as JSON via ajax responses.id
,username
,email
,ip_address
) and treats them specially (giving them formatted names and a Gravatar for email address). It doesn't show any other user data unless the values are part of adata
substructure. This patch makes all of the passed fields visible in Sentry.