You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not 100% sure what Caroline's original intentions were with page template but I would assume she would want component="main" to work as a top level prop, so I'll proceed with the bugfix as such (vs. updating the types)
Fixes#143547
To make sure the correct semantic elements are used, you can pass the
`component` prop to the page template components. As the eui components
`EuiPageTemplate`, `EuiPageTemplate.Section` and so bring styling with
them there's not much value in trying to put them into the places of
manual `section`s used in Lens today because we would end up overruling
all of these default styles anyway as Lens is pretty special in terms of
page layout to make best use of the existing screen real estate.
Because of this this PR is simply turning the `EuiPageTemplate` into a
div and putting the main role to the top level of the Lens app.
The way how to do this is a bit funky right now, but that's an EUI bug
that will be fixed upstream: elastic/eui#6351
Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
The EuiPageTemplate component has some mistmatched types:
component
property which is not respectedmainProps
doesn't have acomponent
property (but it works when specified)The text was updated successfully, but these errors were encountered: