feat(ui5-flexible-column-layout): public layoutsConfiguration property
Add public layoutsConfiguration property to allow the app customize the column proportions per screen size and layout. Also, update the layoutsConfiguration fields whenever the user interactively changes the column proportions by dragging the columns separator.
As synced offline, the layoutsConfiguration is now a public property that is being changed by the component upon user interaction, it would help to fire an event and notify the application about those changes.
Can we discuss which name for the new event is better:
layout-configuration-changelayouts-configuration-changeIn this PR i named itlayout-configuration-change, in analogy to the existinglayout-changeevent. Also, the event fires when the user resizes the column of the current layout he is viewing i.e. upon config change of a single layout. However, given that the corresponding public property islayoutsConfiguration(with "s") would the second option be more consistent?
Can we discuss which name for the new event is better:
layout-configuration-changelayouts-configuration-changeIn this PR i named itlayout-configuration-change, in analogy to the existinglayout-changeevent. However, given that the corresponding public property islayoutsConfiguration(with "s") would the second option be more consistent?
Honestly, I don't have a strong preference for either. Maybe, layout-configuration-change makes more sense semantically as the event detail only includes the layout that chaged. So I personally prefer layout-configuration-change but still choose whichever you prefer.
Can we discuss which name for the new event is better:
layout-configuration-changelayouts-configuration-changeIn this PR i named itlayout-configuration-change, in analogy to the existinglayout-changeevent. However, given that the corresponding public property islayoutsConfiguration(with "s") would the second option be more consistent?Honestly, I don't have a strong preference for either. Maybe,
layout-configuration-changemakes more sense semantically as the event detail only includes the layout that changed. So I personally preferlayout-configuration-changebut still choose whichever you prefer.
OK, the current version seems better indeed. Let us keep it this way then.
:tada: This PR is included in version v2.16.0-rc.3 :tada:
The release is available on v2.16.0-rc.3
Your semantic-release bot :package::rocket: