v1.0.0
What's Changed​
New Features​
- New design #84
- Password reset support #60
- One-time password support #60
- Collaboration server in admin-server #85
- Editor: Sortable blocks and major refactoring including new API for adding custom blocks and bug fixes #71, #76, #82
- Datagrid:
HasOneSelectCell
andHasManySelectCell
#87 - Datagrid: Remembers selected filters and page when navigating back #81
Fixes​
Deprecations​
PageLinkById
usePageLinkButton
instead.PageLink
useLink
instead.PageLinkButton
useLinkButton
instead.
Full Changelog: https://github.com/contember/admin/compare/v0.7.0...v1.0.0-rc.1
Migration​
We've simplified the layout components to make them easier to use. To use the new layout, you need to update a few things.
Mandatory changes​
Rename <Layout />
props​
topStart
tosidebarHeader
topEnd
tosidebarFooter
sideBar
tonavigation
<Layout
topStart={...}
topEnd={...}
sideBar={...}
/>
<Layout
sidebarHeader={...}
sidebarFooter={...}
navigation={...}
/>
Remove <TitleBar />
​
- Move prop
actions
from the<TitleBar />
component to page component (e.g.<Page />
,<GenericPage />
,<LayoutPage />
). - Remove the
<TitleBar />
component and insert the contents of the<TitleBar />
component into thetitle
property of the page.
<GenericPage
pageName="blogList"
>
<TitleBar
actions={...}
>
Article
</TitleBar>
...
</GenericPage>
<GenericPage
pageName="blogList"
title="Article"
actions={...}
>
...
</GenericPage>
Rename <LayoutInner />
and remove <LayoutSide />
​
- Change the
<LayoutInner />
to<LayoutPage />
. - Remove the
<LayoutSide />
component and insert the content into theside
prop on<LayoutPage />
.
<LayoutContent>
<LayoutInner>
...
</LayoutInner>
<LayoutSide>
<PersistButton />
</LayoutSide>
</LayoutContent>
<LayoutContent>
<LayoutPage side={<PersistButton />}>
...
</LayoutPage>
</LayoutContent>
Remove <AltPersistButton />
component​
- We no longer support
<AltPersistButton />
component. Remove it or change it to<PersistButton />
.
Tenant pages​
- Change the
<GenericPage />
component that wraps the tenant pages to<Page />
component.
Recommended changes​
Remove unnecessary <Box />
component​
We added a new <Section />
component that divides groups of fields on a page into logical page sections. The section names are also listed within the navigation on the page tabs. Sections are not intended to be nested within other sections and should only be used to define the top-level sections of a page. Sections must be parent elements to dimensions, not vice versa, due to styling constraints.