Skip to content
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

Wiki - Run ScanAPI Locally #312

Closed
flaviotruzzi opened this issue Oct 10, 2020 · 1 comment
Closed

Wiki - Run ScanAPI Locally #312

flaviotruzzi opened this issue Oct 10, 2020 · 1 comment
Labels
Documentation Improvements or additions to documentation

Comments

@flaviotruzzi
Copy link
Contributor

Hi,

I was following the wiki, it looks like the documentation there is outdated with the current state of the project.

It says:

poetry run scanapi ../examples/pokeapi/scanapi.yaml -c ../examples/pokeapi/.scanapi.yaml -o ../examples/pokeapi/scanapi-report.html

However the example structure does not follow that:

> tree examples/pokeapi
examples/pokeapi/
├── README.md
├── scanapi.conf
├── scanapi-report.html
└── scanapi.yaml

From the help I got it running with:

> poetry run scanapi run examples/pokeapi/scanapi.yaml -c examples/pokeapi/scanapi.conf -o examples/pokeapi/scanapi-report.html
Loading file examples/pokeapi/scanapi.conf
Loading file examples/pokeapi/scanapi.yaml
Writing documentation
Making request GET https://pokeapi.co/api/v2/pokemon
Making request GET https://pokeapi.co/api/v2/pokemon/bulbasaur

The documentation was generated successfully.
It is available at /home/[omitted]/examples/pokeapi/scanapi-report.html

Did I miss something?

@camilamaia camilamaia added the Documentation Improvements or additions to documentation label Oct 19, 2020
@marcuxyz
Copy link
Member

You really are super right! This will be corrected ...

as documentation:
image

with fixed:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants