V4: Additions - NumericValue & ApplicationCommandOptionValue

[Panthr75]

Motivation

After working with numbers in application commands, it was a pain not having a typed value for choice values, as well as values of raw received application interactions. As such, I proposed two new structs

ApplicationCommandOptionValue

This replaces all instances of object for application command option values. This includes in choices, and received interactions.

Internally, it stores all values possible for an option value:

• string
• boolean
• number
• user
• channel
• role
• mentionable
• attachment
• null

Then, you can check if the value is a specific type via the IsX properties. Then, it can be converted to those underlying values via Get methods.

For an implementation, see the current implementation in bonnel-lib

NumericValue

This replaces all instances of double in application commands. This allows users to have more precision, especially when assigning really large long values as min/max values.

Internally, it stores a long, double, and nullable boolean value. This allows for precision via the long part of the numeric value,
and allows for decimals via the double part of the numeric value.

For an implementation, see the current implementation in bonnel-lib

Caveats

• This is a breaking change,
• JSON Converters will need to be written for both of these structs.

Benefits

• Builders wont need separate methods for int, double, float, and long values
• Users of the library have a better idea of what an application interaction value is, with improved type checking
• Improved precision for sending over large long values
• Improved type safety internally