Enable unsafe keep a json specification when compeller is invoked #19
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
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.
closes: #15
This will ensure that when the compeller is invoked it will create a JSON specification file.
This could be a seriously dangerous side effect that would make testing an awful experience and honestly needs a better solution.
One thing could be to add a command to the CLI that can find the typescript file, but it would mean that we need to have a
compeller.jsconfiguration to point at the file location, and I think we have all got enough configuration files in our project.Another option would be to somehow bind to the usage of compeller and find it with the CLI.
TODO