Doc Feedback: Tutorials should be updated to work with VSCode Editor
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
In this tutorial[1], integration part is still guided through Integration Studio which is no longer we propose to customers/prospects. Please update documentation to build integration part with VSCode plugin and expose it as an API in APIM.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked tutorial, especially the “Step 2: Develop the integration service” section, and compare its current Integration Studio workflow with the VSCode plugin workflow. Update the tutorial to build the integration with VSCode and expose it as an API in APIM; the documented steps should work without directing users to Integration Studio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100