We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current CLI is a bit awkward since it was thrown together for the proof-of-concept. Sub-commands could help clean it up a good amount:
postject inject <filename> <resourceName> <resource> [outputFilename]
postject inspect <filename>
postject view <filename> <resourceName>
postject output-api
stdout
The text was updated successfully, but these errors were encountered:
commander
parseArgs
No branches or pull requests
The current CLI is a bit awkward since it was thrown together for the proof-of-concept. Sub-commands could help clean it up a good amount:
postject inject <filename> <resourceName> <resource> [outputFilename]
- the current functionality, but with optional output pathpostject inspect <filename>
- shows you a list of resources injected in the executablepostject view <filename> <resourceName>
- shows you the contents of a resourcepostject output-api
- dumps the C run-time API tostdout
The text was updated successfully, but these errors were encountered: