oaOutput in NPX call doesn't write file
See original GitHub issueI attempted to generate an output and an oaOutput file together using npx
using Gradle. The CLI output indicated the oaOutput file wrote to tmp even though I ensured the filepath existed prior to running the command.
I will say I find it is just as easy to chain a gradle task for OpenAPI-format with the Portman task. I wonder if it might make sense to avoid embedding it, unless it is needed for other purposes.
My current plan is to create the various test sets from my main spec using openAPI-format, then process that through portman to generate the postman collection(s).
Issue Analytics
- State:
- Created 2 years ago
- Comments:9
Top Results From Across the Web
Write output of `npm run start` to a file - Stack Overflow
This will work npm run start 2>&1| tee npm.txt. Explanation: 2>&1 will redirect error stderr to stdout and tee command will write terminal ......
Read more >A Complete Guide to Using TypeScript in Node.js - Better Stack
After saving the file, run the TypeScript compiler once more. You will observe that no output is produced, which means the compilation was...
Read more >tsc randomly produces no output at all and then on ... - GitHub
tsc run with exit code 0. and run fswatch get no file create/modify operation at all. there is no unhandled exception using inspector....
Read more >CLI - Node Tap
If <file> is not present, then all command-line positional arguments are run. After the set of test files are run, any failed test...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Closing this issue. If you still have problems, feel free to re-open or create a new issue.
@ChristineP2 We just released version 1.15.0 of Portman, where the reported issues should be fixed.