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
VSCode extension for ScanAPI IntelliSense #48
Comments
Hi, Obs: In the future we can introduce more advanced features like linting, i think it would be awesome. |
@abreumatheus What a great surprise for a Sunday morning! |
@abreumatheus this looks good for a first version. Next version we can explore the other VSCode APIs. Very excited to see this progressing! @camilamaia I can help you out if needed, creating the MS account. I had to go through the same process for Loadsmart's. Let me know. |
@barbosa All help is welcome, it was the first time i tried to develop a VSCode extension, so there's a lot to learn. 😃 |
Very excited seeing this happening, @abreumatheus. Thank you so much for digging into their API! 💪 |
@abreumatheus wow, wow, wow! This is amazing 🚀 🤩 Thanks for that! I am super excited with it. Let me see to create the MS account |
@camilamaia Thanks! Don't forget the repo here on github, so i can push it there and we'll be able to start contributing 😃 |
@abreumatheus oh, good point! 😅 let me do it right now! |
@barbosa and I just created the Microsoft Account and set the token in the secrets of the new repo. This way we can automatize the deploy: scanapi/vscode-extension#1 We also did a first release manually only for testing: 🎉🎉🎉 |
I am going to close this issue because now we can starting creating specific issues in the new repo. |
Given that ScanAPI already has a predefined yml structure, we could have a VSCode extension that autocompletes keys (
endpoints
,method
,path
, etc) based on where you are in the spec tree.This would require further investigation to see what can be achieved but the following links should give some clarity:
The text was updated successfully, but these errors were encountered: