Skip to content
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

feat: Manually capturing user feedback #805

Merged
merged 4 commits into from
Oct 21, 2020
Merged

Conversation

philipphofmann
Copy link
Member

@philipphofmann philipphofmann commented Oct 20, 2020

📜 Description

The SentrySDK now provides a method captureUserFeedback to associate user feedback to an event. A callback to send user feedback after a hard crash is going to be delivered in another PR.

💡 Motivation and Context

We want to bring this awesome feature to our customers.

💚 How did you test it?

Unit tests and with a simulator.

📝 Checklist

  • I reviewed the submitted code
  • I added tests to verify the changes
  • I updated the CHANGELOG
  • I updated the docs if needed
  • No breaking changes

🔮 Next steps

The SentrySDK now provides a method captureUserFeedback to associate user
feedback to an event.
@philipphofmann philipphofmann changed the title feat: Manually capturing User Feedback feat: Manually capturing user feedback Oct 20, 2020
@philipphofmann philipphofmann requested a review from a team October 20, 2020 11:55
@philipphofmann philipphofmann marked this pull request as ready for review October 20, 2020 14:59
/**
* Adds additional information about what happened to an event.
*/
NS_SWIFT_NAME(UserFeedack)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

m: Because we were talking about this at the standup, should we call this now also SentryUserFeedback in Swift? @bruno-garcia, @marandaneto and @jennmueng

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that UserFeedback is a more specific name, I have no strong feelings here.

I rather default to SentryName when the name is super generic like Client or Event.

Copy link
Member

@bruno-garcia bruno-garcia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

/**
* Adds additional information about what happened to an event.
*/
NS_SWIFT_NAME(UserFeedack)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that UserFeedback is a more specific name, I have no strong feelings here.

I rather default to SentryName when the name is super generic like Client or Event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature: User Feedback
2 participants