Closed Ruttie2006 closed 9 months ago
👋🏽 Hi! Thanks for opening this issue. The stacktrace you've provided points to these lines being the culprit:
I'll be looking into why this is the case momentarily.
With some investigative help from Vamplay on Discord, it turns out this is due to a breaking change in .NET 8. PR inbound.
Any updates on a possible fix? I would like to use optional parameters, but because of this I can't really...
@VelvetToroyashi
Last I recall @DPlayer234 had implied they would fix it, but I can PR their changes if need be https://canary.discord.com/channels/789912892426027039/789913038920744960/1163523508924579880
@VelvetToroyashi I didn't mean to imply I'd make a PR. Feel free to go ahead.
I don't mean to be pushy, but is there any update on this? ( @VelvetToroyashi )
Hi sorry, I've been caught up with various projects. I'd have to look through my branches to see if I've already fixed this, but otherwise 'no', I'm afraid.
Description
When an optional parameter is added to a slash command, and that slash command is executed without said paramater, an exception occurs.
Steps to Reproduce
Code:
Replace constants with applicable values.
Expected Behavior
Command should execute without the parameter being set.
Current Behavior
The following exception is printed in the console, and the command is not executed:
Library / Runtime Information
Used packages:
.NET version: 8.0 LangVersion: preview (12)