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
...
As the display for dredd doens't actually show which whitespace is from the parser, and which is formatting from dredd, it's... not easy to catch.
You can wrap it with a hook, which I'll do for the tests, but I'm going to suggest a - whitespace option to display \n, \t, \s or similar for 'eyeball' tests.
So according to the suggestion, dredd's output would use some visible notation for various forms of whitespace so one could easily see the difference in case the only mismatch is in type of whitespace or X spaces vs. tab, etc.
The text was updated successfully, but these errors were encountered:
Coming from a suggestion on API Blueprint Slack channel:
So according to the suggestion, dredd's output would use some visible notation for various forms of whitespace so one could easily see the difference in case the only mismatch is in type of whitespace or X spaces vs. tab, etc.
The text was updated successfully, but these errors were encountered: