Json to plist build #8
Merged
Conversation
This file contains hidden or 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
…list Use the part after `.JSON-` as new extension to be compatible with `.JSON-tmLanguage` (which is not a bad standard at all) Use simple `.plist` for `.json` files
…ector value so Sublime's auto-detection of build system works for these
(btw, it is not *always* necessary to reload a syntax definition file; rather rarely)
Member
|
Looks good to me. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I modified the "make_tmlanguage" command (and the build system) to convert any JSON file into a Property List and getting the new extension from the current extension in a format like the good old ".JSON-tmLanguage".
Additionally I added a selector to the build system so it would be auto-detected by Sublime Text.