Struct relay_event_schema::protocol::UserReport

pub struct UserReport {
    pub event_id: EventId,
    pub name: String,
    pub email: String,
    pub comments: String,
}

User feedback for an event as sent by the client to the userfeedback/userreport endpoint.

Historically the “schema” for user report has been “defined” as the set of possible keyword-arguments sentry.models.UserReport accepts. Anything the model constructor accepts goes.

For example, {"email": null} is only invalid because UserReport(email=None).save() is. SDKs may neither send this (historically, in Relay we relaxed this already), but more importantly the ingest consumer may never receive this… because it would end up crashing the ingest consumer (while in older versions of Sentry it would simply crash the endpoint).

The database/model schema is a bunch of not-null strings that have (pgsql) defaults, so that’s how we end up with this struct definition.

Fields

event_id: EventId

The event ID for which this user feedback is created.

name: String

The user’s name.

email: String

The user’s email address.

comments: String

Comments supplied by the user.

Trait Implementations

impl Debug for UserReport

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for UserReport

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for UserReport

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.