Interaction command options now have separate fields for the different possible values e.g.
# Simple example of behind the scenes
let input = %* {
"value": "foobar",
"type": 3,
"name": "word"
}
let option = input.newApplicationCommandInteractionDataOption()
# Code that the developer would write
assert option.str == "word" # isn't an option anymore
assert option.ival == 9 # Throws an error since option.kind != acotInt
Also wrote some unit tests based on json responses from discord to test that this works in different scenarios
Interaction command options now have separate fields for the different possible values e.g.
Also wrote some unit tests based on json responses from discord to test that this works in different scenarios