You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When I have a string option and I enter numbers separated by commas, the first comma is always replaced by a dot.
It seems that the error does not occur in the API, but in the client that converts it when sending it.
Steps to Reproduce
Have a string option
Enter some numbers separated by commas (ej: 1,2,3) without whitespaces.
Send the command and check the received interaction or the sent command info.
Expected Behavior
Doesn't convert the first comma into a dot
Current Behavior
It converts the first comma into a dot
Screenshots/Videos
Interaction payload:
Client and System Information
Canary 99031 (720b494)
Host 1.0.42
Windows 11 64-Bit (10.0.22000)
The text was updated successfully, but these errors were encountered:
This only affects people whose discord language is set to a language which uses a comma as a decimal separator. This issue was reported in ddevs on 30th august and was apparently logged as a bug. No idea what happened afterwards and it seems like it's not fixed.
I can also reproduce this when using discord in French.
Description
When I have a string option and I enter numbers separated by commas, the first comma is always replaced by a dot.
It seems that the error does not occur in the API, but in the client that converts it when sending it.
Steps to Reproduce
1,2,3
) without whitespaces.Expected Behavior
Doesn't convert the first comma into a dot
Current Behavior
It converts the first comma into a dot
Screenshots/Videos
![vKR3QFh5mv](https://user-images.githubusercontent.com/33096355/134778653-08109c26-869d-4980-94c8-d8e1ee1abc86.gif)
Interaction payload:
![image](https://user-images.githubusercontent.com/33096355/134778675-3e4303ac-dd2f-4ddc-a5b9-579b4cc03c6f.png)
Client and System Information
Canary 99031 (720b494)
Host 1.0.42
Windows 11 64-Bit (10.0.22000)
The text was updated successfully, but these errors were encountered: