AVAP API Source Control
Advanced tools
The AVAP API Source Control extension for Visual Studio Code makes it easy to build and manage versions of your AVAP APIs.
To get started, check out: Working with AVAP API Source Control extension for Visual Studio Code at AVAP Alexandria, our resource site, alexandria.avapframework.com. You can also find more information at AVAP Developer Portal developer.avapframework.com.
Find troubleshooting tips and additional technical information at AVAP Communities, communities.avapframework.com
AVAP API Source Control requires the installation of the base extension, AVAP Dev Extensions for Visual Studio Code
The AVAP API Source Control extension for Visual Studio Code offers support when running on vscode.dev. This includes free access to alexandria.avapframework.com and communities.avapframework.com.
The AVAP API Source Control extension for Visual Studio Code will not install any other extension. It is necessary to install the base extension: AVAP Dev Extensions for Visual Studio Code.
Step 1. Install the AVAP API Source Control extension.
Step 2. You can now view all your environments, APIs, and tests per environment.
Step 3. Create a new API.
Step 4. Create a new AVAP (.avap) file or use the proposed template to start coding!
The AVAP API Source Control for Visual Studio Code allows you to navigate between different environments in your deployment, creating new APIs or managing versions of existing APIs
AVAP CLI gives you access to the full AVAP management command set in an isolated environment. For more information on available commands, see Get started with AVAP CLI.
AVAP API Source Control extension for Microsoft Visual Studio Code
Copyright (c) 101OBEX Corp.
All rights reserved.
MIT License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
AVAP API Source Control
We found that 101obexcorp.101obex-api-extension-api-code demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
The North Korean malware loader hides in a Packagist-listed package and its GitHub branch to fetch and execute remote code in a likely Contagious Interview-style lure.
Security News
The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and contributor experience.
Research
/Security News
A malicious NuGet package impersonating Sicoob exfiltrated client IDs, PFX passwords, and banking certificates through Sentry telemetry.
