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.

Sign up for GitHub

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

Jump to bottom

Multiple terms used to introduce inbound endpoints #568

Open
DinithiDiaz opened this issue Dec 20, 2024 · 0 comments
Open

Multiple terms used to introduce inbound endpoints #568

DinithiDiaz opened this issue Dec 20, 2024 · 0 comments
Labels
Type/Improvement

Comments

@DinithiDiaz
Copy link
Member

Current Limitation

When creating an inbound endpoint, there are multiple terms used in the UI: inbound endpoint, listener, and trigger.

inbound-ep

Suggested Improvement

Can we finalize a single name? Using multiple names for the same artifact might confuse users.

Version

No response
@DinithiDiaz DinithiDiaz changed the title Multiple terms used to introduce iInbound endpoints Multiple terms used to introduce inbound endpoints Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type/Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DinithiDiaz