#Nyxi

1 messages · Page 1 of 1 (latest)

meager flameBOT
fierce parcel
#

Hi, I'm unsure if this is missing a part

#

Can you clarify the ask here please?

shy acorn
#

No it's complete. Hehe. Sometimes you'll get an array of events for an action that you didn't expect, so having a flowchart of "making requests to this endpoint may trigger the following events:"

#

It's not always clear

#

Well, doesn't need to be af flowchart, of course, but just a list of possible events could be helpful

#

Like above; it's not totally obvious that charge.refunded would fire for a charge that was never captured

fierce parcel
#

Ahhh I see

#

Sorry, had to read it again

shy acorn
#

And it will send that, but it will also send charge.refunded

#

(asssuming you subscribe, of course)

fierce parcel
#

Thank you, I'll share this feedback with the team.

shy acorn
#

It could just be an expandalbe list of "This endpoint may trigger the following events:" on each endpoint

#

and of course, it would be up to you to figure out if it applies to your case, but at least you'd know to consider it

fierce parcel
#

Yeah... I think the tricky part would be 'This event may trigger' and people would automatically expect this event.. If they don't see it breaks their code. However, I do see your point and I'll share it with the team.

#

Thank you!