New issue
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
Change command "scanapi <spec_file>" to "scanapi run <spec_file>" #247
Conversation
|
Obs: It's failing on |
CHANGELOG.md
Outdated
| @@ -17,6 +17,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
| - Renamed `api.(yaml|json)` to `scanapi.yaml` [#222](https://github.com/scanapi/scanapi/issues/20://github.com/scanapi/scanapi/pull/222) | |||
| - Remove top-level `api` key in `scanapi.yaml`. [#231](https://github.com/scanapi/scanapi/pull/231) | |||
| - Renamed `project-name`, `hide-request` and `hide-response` to use underscore. [#228](https://github.com/scanapi/scanapi/issues/228) | |||
| - Changed command `scanapi <spec_file>` to `scanapi run <spec_file>`. [#247](https://github.com/scanapi/scanapi/pull/247) | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abreumatheus just a wild guess here can you try
- Renamed change command "scanapi <spec_file>" to "scanapi run <spec_file>" [#247](https://github.com/scanapi/scanapi/pull/247)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's weird that the stack trace of circleci dosen't give out any error message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weird
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abreumatheus Now you got a different error. See:
-- Changed command "scanapi <spec_file>" to "scanapi run <spec_file>" [#247](https://github.com/scanapi/scanapi/pull/247)
+- Changed command "scanapi " to "scanapi run " [#247](https://github.com/scanapi/scanapi/pull/247)Apparently the tool is cutting out everything in between < >
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@barbosa Yeah, it wasn't it. Apparently Circle CI just hates me
Edit: I'm installing the linter used by Circle CI, will use it on the file and see if it corrects any invisible errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abreumatheus was it just the empty space in the end that was causing this issue ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abreumatheus was it just the empty space in the end that was causing this issue ?
Honestly, i dont even know, just ran the linter locally and saved the output to a new file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay. I saw the diff in the end and the only thing I could make out of it was that space xp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow, this was a nice team effort, what a battle
|
@camilamaia just a suggestion once the PR is ready to merge we can ask the PR creator to squash all the commits into one commit. That would help us in a cleaner git history too. |
|
@camilamaia Yes, but if we squash and merge it still gives out This commit message is more or less noice for folks who aren't involved in the PR. If the PR creator squashes and merges he/she/they can put a single appropriate commit message that can be really helpful for other people too who weren't involved in the PR. Something like: ( Do correct me if I am wrong) PS: I tagged you spectrum thinking the notification won't go as the branch is deleted. So feel free to ignore that. :) |
|
@Pradhvan hmm that makes sense. We can use this approach in the next PRs! I use a lot —amend command, so I am not that used with squash. Good to know |
Closes: [#226 ]
Changed
scanapi <spec_file>toscanapi run <spec_file>.