[Flyout System] improve size validation flexibility and bidirectionality #9094
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
sso that default sizing for both parent and child results in a valid combinationWhy are we making this change?
We have to allow flexible sizing options to support existing use cases in Kibana and provide an easy migration path for those flyouts to adopt the Flyout System.
Screenshots #
Impact to users
Impact to devs: easier migration path to adopt existing flyouts into the Flyout System.
QA
Remove or strikethrough items that do not apply to your PR.
General checklist
@defaultif default values are missing) and playground toggles