-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be able to create a non-indented uReport #104
Comments
The whitespace is pretty much hardcoded in the json output procedures (surely can be stripped though).
|
|
Note to future self: work in progress regarding this ticket has been pushed to branch |
Well, I'd rather work up a bit more systematic and reliable solution instead of removing redundant white space from JSON formatted text :) How about to stop insisting on the design where JSON is the only supported output format? |
Care to elaborate? IMHO, the current design does not in any way prevent adding support for other output formats. I agree that removing the white space after the JSON-formatted text is generated is retarded, but it is the least time-consuming approach due to the nature of the formatting code. |
At the moment satyr generates a nicely indented uReport, which is perfectly human-readable, but a little non-practical for sending over network. For example the following uReport contains 50% of unnecessary white spaces (satyr generates 35686 bytes, json.dumps() for the very same report only gives 17843)
The text was updated successfully, but these errors were encountered: