Skip to content

Commit

Permalink
reference: be consistent with example code
Browse files Browse the repository at this point in the history
Signed-off-by: Luca Zeuch <[email protected]>
  • Loading branch information
l-zeuch committed Nov 17, 2024
1 parent 0aab300 commit 97d1a64
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions content/docs/reference/custom-interactions.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,8 +183,8 @@ We have also set the `max_values` to 3, and we haven't set a `min_values` argume
server member could select anywhere between 1 and 3 of these options.

If the member selected all three options and submitted it (which would send an interaction to YAGPDB), while [parsing
that interaction](#parsing-an-interaction) the `.Values` context data would be `["opt-1" "duck-option" "opt-3"]`. This is
because in our code defining the select menu, we defined the `"value"` args of our menu options as `opt-1`,
that interaction](#parsing-an-interaction) the `.Values` context data would be `["opt-1" "duck-option" "third-option"]`.
This is because in our code defining the select menu, we defined the `"value"` args of our menu options as `opt-1`,
`duck-option`, and `third-option`. If the member only selected the "Half a Duck" option, `.Values` would be
`["third-option"]`.

Expand Down

0 comments on commit 97d1a64

Please sign in to comment.