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
I noticed that the fixtures for testing the formats all seem to use roughly the same input format, with the properties named using the constant-convention-esque UPPER_SNAKE_CASE.
This means the tests really only cover your cases if you use the same naming convention for your tokens. Since theo's users probably have more diverse input, I wonder if you'd be open to more diverse fixtures that will also provide more complete coverage of what the formats are actually doing (some of the functions applied to e.g. property names will change the output of things like spaces and hyphens, which aren't being reflected in/covered by the test suite currently).
I noticed that the fixtures for testing the formats all seem to use roughly the same input format, with the properties named using the constant-convention-esque UPPER_SNAKE_CASE.
This means the tests really only cover your cases if you use the same naming convention for your tokens. Since theo's users probably have more diverse input, I wonder if you'd be open to more diverse fixtures that will also provide more complete coverage of what the formats are actually doing (some of the functions applied to e.g. property names will change the output of things like spaces and hyphens, which aren't being reflected in/covered by the test suite currently).
The text was updated successfully, but these errors were encountered: