-
-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PageContainer] Allow full-size content #4480
base: master
Are you sure you want to change the base?
[PageContainer] Allow full-size content #4480
Conversation
@@ -1,5 +1,5 @@ | |||
{ | |||
"props": {}, | |||
"props": { "children": { "type": { "name": "node" } } }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proptypes are now being generated for the components which don't match the name of the folder (secondary components), I think that should be a good thing?
Changed it in the script that generates proptypes so that the API documentation for PageHeader
would be there, auto-generated.
@@ -204,7 +204,7 @@ async function run(argv: HandlerArgv) { | |||
folderName = folderName.slice(9); | |||
} | |||
|
|||
return fileName === folderName; | |||
return !fileName.endsWith('.test'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generates proptypes for all non-test files inside the folder of each component.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is also generating proptypes for components marked as @ignore
in the JSDoc comments - something to fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we can try to exclude them if it's easy to do.
done!
Looks like the CI is having out of memory issues again, we probably either need to manage dependencies to stay under or increase instance sizes? |
Yes, although I'm wondering what exactly triggered the CI out of memory issues |
docs/data/toolpad/core/components/page-container/page-container.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just some suggestions on the docs demo and one flag on the proptypes script.
Also, I'm guessing this counts as a breaking change since we are renaming PageContainerToolbar
to PageHeaderToolbar
docs/data/toolpad/core/components/page-container/PageContainerHeader.tsx
Outdated
Show resolved
Hide resolved
…r.md Co-authored-by: Bharat Kashyap <[email protected]> Signed-off-by: Pedro Ferreira <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Closes #4324
Needed it already in the CRUD for the list table to take up the full space in the layout.
As per the discussion in #4324:
PageContainer
withflex: 1
orheight: 100%
.sx
prop toPageContainer
.PageHeader
fromPageContainer
to optionally be used as a standalone componenthttps://deploy-preview-4480--mui-toolpad-docs.netlify.app/toolpad/core/react-page-container