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
Small inconsistency found in the way gravity parses strings. Let's say the Gravity.ini file looks as follows:
string1 = "message"
String1 = "Message"
int1 = 9;
Int1 = 10;
The second key is the same as the first except that the first letter is capitalized. For ints, floats, and booleans, the value of the first key will be stored. So when the user parses for int1 or Int1, they will always get back 9. The string parser is the only one that is inconsistent with this. When the user parses for string1 or String1, they will get back "Message", the second value.
This is a corner case and unlikely to make a big difference in practice, but still thought it important to document. The unit tests are currently testing for this consistency.
The text was updated successfully, but these errors were encountered:
Small inconsistency found in the way gravity parses strings. Let's say the Gravity.ini file looks as follows:
string1 = "message"
String1 = "Message"
int1 = 9;
Int1 = 10;
The second key is the same as the first except that the first letter is capitalized. For ints, floats, and booleans, the value of the first key will be stored. So when the user parses for int1 or Int1, they will always get back 9. The string parser is the only one that is inconsistent with this. When the user parses for string1 or String1, they will get back "Message", the second value.
This is a corner case and unlikely to make a big difference in practice, but still thought it important to document. The unit tests are currently testing for this consistency.
The text was updated successfully, but these errors were encountered: