-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
no JSON whitespace in release version #886
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rurban
reviewed
Dec 2, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea, but better as runtime cmdline switch. like --json-compact or so
and without dxfread
rurban
added a commit
that referenced
this pull request
Feb 7, 2024
no whitespace at run-time. We don't write minimal JSON as with minimal DXFs anymore ($ACADVER, $HANDSEED, and then ENTITIES only). With ideas from GH #886
I've used now --fmt=minJSON or --outfile=xxx.min.json for this feature. And your FSF CLA doesn't come along in time |
see smoke/minjson-gh886 |
rurban
added a commit
that referenced
this pull request
Feb 7, 2024
no whitespace at run-time. We don't write minimal JSON as with minimal DXFs anymore ($ACADVER, $HANDSEED, and then ENTITIES only). With ideas from GH #886
rurban
added a commit
that referenced
this pull request
Feb 7, 2024
no whitespace at run-time. We don't write minimal JSON as with minimal DXFs anymore ($ACADVER, $HANDSEED, and then ENTITIES only). With ideas from GH #886
rurban
added a commit
that referenced
this pull request
Feb 8, 2024
no whitespace at run-time. We don't write minimal JSON as with minimal DXFs anymore ($ACADVER, $HANDSEED, and then ENTITIES only). With ideas from GH #886
rurban
added a commit
that referenced
this pull request
Feb 8, 2024
no whitespace at run-time. We don't write minimal JSON as with minimal DXFs anymore ($ACADVER, $HANDSEED, and then ENTITIES only). With ideas from GH #886
rurban
added a commit
that referenced
this pull request
Feb 8, 2024
no whitespace at run-time. We don't write minimal JSON as with minimal DXFs anymore ($ACADVER, $HANDSEED, and then ENTITIES only). With ideas from GH #886
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Saves almost half the size; I plan to use this in a javascript production environment.