Add more file extensions or Configurable file extensions?#73
Open
woshiZS wants to merge 2 commits intostef-levesque:masterfrom
Open
Add more file extensions or Configurable file extensions?#73woshiZS wants to merge 2 commits intostef-levesque:masterfrom
woshiZS wants to merge 2 commits intostef-levesque:masterfrom
Conversation
Update package.json to support .es extension
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 am wondering if the file extensions for shading language can be configurable(either add a configure file or add a new command option).
Shadeing Language files are plain text files and may have any extension names, so I think this will help those who write shader files with extensions not in the current extension lists.
As for this pr, I only add an extension to the package.json(forgive me, I am not familiar with typescript).