Introduction
Welcome to eWam VSCode extension!
The current version focuses on Debug features. You still need the regular eWam IDE as well as a license to do develop your project.
eWam is a proprietary product of Mphasis Wyde, offering a rich set of features including its own language, a comprehensive and powerful metamodel for defining and managing your data structures, integration with relational databases, cloud-native capabilities, API services, and more!
Contact us if you are interested!
In a future version, this extension will include IDE features!
This project is leveraging the eWam APIs.
The Debugging architecture is designed as a "client-server" style. The extension is implementing an adapter following the Debug Adapter Protocol. eWam, running on the "back", is the debugger.
The main use case is to launch an eWam application and attach to it with the extension.
Requirements
VS Code setup
- Use VSCode
- Install the extension
Features
Below the list of features embedded in the extension.
Language
eWam's language is waml (Wyde Active Modeler Language). The corresponding file extension is .wam.
- open
.wam file
- syntax highlighting for
waml
Debug
- Debug Adapter
Leveraging eWam Inspector API.
- attach to eWam processes
- virtual sources display
- debug actions on a given thread (continue/pause, step over, step into, step out)
- breakpoints
- callstack
- data inspection
- commands inside the
Debug Console panel (cli equivalent to any UI of data inspection, run help for details)
- eWam traces file
.wamt view
Doesn't require eWam.
- open
.wamt file
- watch a folder for
.wamt files
- Memory monitoring view
On a given eWam process. Leveraging eWam Memory API.
Workspace configuration
To use the debug features, outside of .wamt files handling, you need the configuration ewamdbg-pool:
- open
Run and Debug
- open
launch.json (if the file doesn't exist then click on create a launch.json file)
- click on
Add Configuration...
- in the dropdown list, select
WAM-PipePool: Launch
Contributors : How to build the extension
- clone
dev/1.x
- npm run build
output is a .vsix in dist folder
