Refactor ui5-calendar's onAfterRendering logic

[vladitasev]

Feature Request Description

Currently, there is a mix of responsibilities in ui5-calendar regarding the knowledge of picker specifics and rendering the header buttons. This is manifested in onAfterRendering where the calendar needs to access the pickers in order to correctly render the header buttons.

Proposed Solution

Refactoring suggestion (but other options are welcome):

• The "calendar header" part is no longer part of the calendar itself - each picker will render its own header (as the individual pickers have the knowledge how to render these buttons, not the calendar)
• However, reuse the ".tsx" template for the header across all pickers (just the logic will be different)
• When a button is pressed, the picker will fire an event to the calendar and the calendar will switch pickers, which in turn will render their own headers etc.

Proposed Alternatives

No response

Organization

No response

Additional Context

No response

Priority

Low

Privacy Policy

• I’m not disclosing any internal or sensitive information.

[dobrinyonkov]

Hello @SAP/ui5-webcomponents-topic-b,

could you please check this refactoring suggestion?

Kind Regards,
Dobrin