You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This approach, while functional, can be verbose and less intuitive for developers who frequently need to access channels by their address.
Proposed Solution
I propose the addition of a getByAddress or a similar function to the parser-api. This function would allow users to directly retrieve a channel based on its address in a more concise and readable manner. The proposed usage would be:
parsedAsyncAPI.channels().getByAddress(address)
The text was updated successfully, but these errors were encountered:
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
I like it. My only concern is that multiple channels can have the same address so I think it should become .filterByAddress() instead. The method should return a collection (not an array), so we can filter it using other helper methods proposed at #105.
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Context
I currently retrieve a channel based on its address using the following code snippet:
This approach, while functional, can be verbose and less intuitive for developers who frequently need to access channels by their address.
Proposed Solution
I propose the addition of a
getByAddress
or a similar function to the parser-api. This function would allow users to directly retrieve a channel based on its address in a more concise and readable manner. The proposed usage would be:The text was updated successfully, but these errors were encountered: