Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Bad Hex String Conversion in Command Sender #908
Describe the bug
"00e5" becomes "0.0" (Expected is "00e5")
Environment (please complete the following information):
@jasonatball Thanks for responding!
That's an interesting workaround which fixes my issue.
That said, for my usage, the parameter that is being incorrectly converted is supposed to be a fixed/pre-calculated value. Needing to go through and add quotes around these String parameters will become very annoying and also not particularly representative of our intended use case.
As a suggestion, would it be possible to have COSMOS automatically add quotes around parameters pulled from workbooks that are designated as Strings? This way, the workaround will be incorporated by default with the added benefit of providing a visual confirmation that the value for the parameter is of type String.
I apologize. The terminology I used was incorrect.
What I meant was a target configuration/definition file. We have a command definition file that contains a line that is similar to this:
The code that receives this command is expecting it as a hex string. The issue right now is that the Command Sender appears to take that command definition file, and adds uses that specified ("00e5") string without quotation marks.
Hopefully this clarifies the issue.