Skip to content
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

[New Feature]: Simplifying Listeners in WSO2 MI #3592

Open
arunans23 opened this issue Sep 6, 2024 · 0 comments
Open

[New Feature]: Simplifying Listeners in WSO2 MI #3592

arunans23 opened this issue Sep 6, 2024 · 0 comments

Comments

@arunans23
Copy link
Member

arunans23 commented Sep 6, 2024

Description

The current WSO2 MI VSCode extension interface for managing inbound connections (Inbound Endpoints and Listener Proxies) is complex and unintuitive, hindering developer productivity which needs to be simplified.

Describe your problem(s)

  • Information Overload: The current UI overwhelms users with separate listings for Inbound Endpoints and Listener Proxies, even though they are conceptually linked.
  • Steep Learning Curve: New users struggle to understand the relationship between these artifacts and their configuration within the VSCode extension.

Describe your solution(s)

The solution has to be designed with minimal changes to MI runtime and mainly focus on UI and documentation aspects.

  1. A Simplified Listener (Inbound Endpoint) development guide.

  2. Simplified Listener View:

  • Introduce a dedicated "Listeners" view within the VSCode extension.
  • This view will consolidate and display all configured listeners, abstracting away the underlying Inbound Endpoint and Listener Proxy configurations.
  • Each listed listener will provide essential information at a glance, such as protocol, port, and associated APIs/services.
  1. Intuitive Configuration:
  • Offer a user-friendly interface within the "Listeners" view to create, edit, and delete listeners.
  • The configuration interface will guide users through the essential settings for common protocols, without exposing the complexities of Inbound Endpoint and Listener Proxy configurations.
  1. Advanced View (Optional):
  • For experienced users who require fine-grained control, provide an optional "Advanced View" within the Listener configuration.
  • This view can expose the underlying Inbound Endpoint and Listener Proxy settings, allowing for customized configurations.

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant