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

Implement Binding Version Check to Ensure Compatibility and Stability #570

Closed
KhudaDad414 opened this issue Nov 12, 2023 · 3 comments
Closed
Labels
enhancement New feature or request stale

Comments

@KhudaDad414
Copy link
Member

Reason/Context

AsyncAPI's strength lies in its extensibility through protocol bindings. These bindings are independently versioned, and Glee's support is tied to specific binding versions. Changes or updates in these bindings can potentially disrupt Glee's functionality or lead to unexpected behavior.

Description

To enhance robustness and user awareness, Glee should implement a version check for protocol bindings. Before parsing, Glee needs to verify if the binding version is one that it currently supports. If the version is unsupported, Glee should issue a clear warning. This warning should inform the user that while Glee will attempt to work with the provided bindings, this might lead to system instability. Additionally, it should prompt the user to report this incompatibility by opening a new issue in the Glee repository, requesting support for the newer binding version.

Solution

Integrate this feature directly into Glee's core functionality. Adapter modules should declare the binding versions they support. Glee, in turn, should handle the compatibility checks based on these declarations. This approach centralizes version management within Glee, simplifying the process for both developers and users.

@KhudaDad414 KhudaDad414 added the enhancement New feature or request label Nov 12, 2023
@ayush3160
Copy link

@KhudaDad414 , Can I work on this ?

@KhudaDad414
Copy link
Member Author

yes, feel free to pick it up. @ayush3160

Copy link
Contributor

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.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label May 17, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

2 participants