You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 13, 2021. It is now read-only.
I am in the same boat as you where I do not want to go to the Zally web ui all the time.
I have installed the vscode extensions and I have a setup of the Zally server where the url is configure in the vscode extensions configuration as mention. How to I use the tool after configuration?
I would recommend that this is added to the readme file.
Thanks.
The text was updated successfully, but these errors were encountered:
Sorry for the late reply. I was held up for medical reasons.
There is no additional step to undertake. However there are currently some pretty big caveats tho.
It currently has to start with openapi: for the linter to pick it up which I guess makes json be bugged. This was to prevent every yaml/json to trigger zally. Going to look into using yaml and json tools to make this work properly.
I had pretty much written this on an evening between two workdays and it needs some cleaning. I am looking into fixing this soon. Sorry for the inconvenience .
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi GoGoOtaku,
I am in the same boat as you where I do not want to go to the Zally web ui all the time.
I have installed the vscode extensions and I have a setup of the Zally server where the url is configure in the vscode extensions configuration as mention. How to I use the tool after configuration?
I would recommend that this is added to the readme file.
Thanks.
The text was updated successfully, but these errors were encountered: