Closed veljko3ap closed 1 year ago
Thank you @veljko3ap. We will check it.
@markus-walther
const versionInfo = __VERSION_INFO__;
defineVersioned([AXADropdown], {'axa-dropdown': versionInfo['axa-datepicker']});
is a workaround at the end of the datepicker's constructor. Unless we understand deeper why the bug suddenly occurred, we could split defineVersioned into simpler-to-understand individual functions that each handle one versioning subcase only. Note, though, that we have to care about the case of multiple PL dependencies in a given component (not evidenced by the datepicker, but elsewhere, e.g. axa-top-content-bar).
We are aware of this bug and will work on it as soon as we have capacity. In the meantime, npm versions prior to the bug are of course usable - please use them wisely for your applications.
Starting from the latest version of Datepicker dropdowns for months and years are not displayed anymore in our latest eSalesP web app for vehicle insurance.
Expected Behavior
Dropdowns for months and years should be displayed in datepicker.
Current Behavior
At the moment users are not able to select desired month and/or year in datepicker.
Steps to Reproduce
Context (Environment)
This happens in all environments localhost, prod. OS, browser doesn't matter.
Possible Solution
Pass on pod name as version suffix to dropdown inside datepicker?