We are pleased to announce the release of Driver Manager version 0.1.1. This release includes critical fixes enhancing the functionality and reliability of the driver support checks and the management of enabled drivers within the system. Below are the detailed changes included in this update:
Enhancements and Fixes:
-
Support Check for Both Attribute and Contract (Issue #1): The
supportsmethod within theDriverManagerhas been updated to correctly check for both attribute and contract requirements when both are not null. This ensures a more stringent validation process, allowing the system to accurately determine if a class is supported based on the defined attribute and contract configurations. This update addresses a crucial requirement where a class must use both the attribute and contract to be considered supported, enhancing the specificity and reliability of driver support checks. -
Driver Enabled Check Using
array_key_exists(Issue #2): We've fixed an issue in theisEnabledandgetmethods of theDriverManager, where the check to determine if a driver is enabled was incorrectly usingisset, which failed to recognize drivers loaded with a null value. By switching toarray_key_exists, we ensure accurate detection of whether a driver is enabled, regardless of its current value. This fix corrects the behavior where drivers were always determined to be disabled, improving the manager's ability to accurately track and manage the state of loaded drivers.
Closing Notes:
This update addresses key aspects of the Driver Manager's functionality, making it more robust and reliable. We encourage all users to update to version 0.1.1 to benefit from these improvements.
For any issues or contributions, please visit our project repository. We appreciate your feedback and contributions to making the Driver Manager better with each release.