Skip to content
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.

Sign up for GitHub

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

[core] Fix Vale errors #4347

Merged
merged 1 commit into from
Nov 2, 2024
Merged

[core] Fix Vale errors #4347

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/data/toolpad/core/components/account/account.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ When signed out, the component renders as an inline sign in button within the da

## Customization

The `<Account />` component is composed of multiple sub-components:
The `<Account />` component is composed of multiple subcomponents:
Copy link
Member Author

@oliviertassinari oliviertassinari Nov 1, 2024 •
edited by bharatkashyap
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was reported in https://github.com/mui/toolpad/pull/4181/files

SCR-20241101-szvn

See PR description (mui/mui-public#226 (comment)) for why it didn't break the CI.


- `<SignInButton />`
- `<AccountPreview />`
Expand All @@ -53,7 +53,7 @@ You can pass in your own components inside the `Account` popover through the `sl

#### Popover Content

You can wrap the default sub-components – such as `SignOutButton` and `AccountPreview` – and wrap them in `AccountPopoverHeader` and `AccountPopoverFooter` components to create custom account popovers, as shown in the following demos:
You can wrap the default subcomponents – such as `SignOutButton` and `AccountPreview` – and wrap them in `AccountPopoverHeader` and `AccountPopoverFooter` components to create custom account popovers, as shown in the following demos:

##### Account Switcher

Expand Down
8 changes: 4 additions & 4 deletions docs/data/toolpad/core/introduction/integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,12 +53,12 @@ You can find details on the `AppProvider` props on the [AppProvider](/toolpad/co
:::info
The `AppRouterCacheProvider` component is not required to use Toolpad Core, but it's recommended to use it to ensure that the styles are appended to the `<head>` and not rendering in the `<body>`.

See the [Material UI Next.js integration docs](https://mui.com/material-ui/integrations/nextjs/) for more details.
See the [Material UI Next.js integration docs](https://mui.com/material-ui/integrations/nextjs/) for more details.
:::

### 2. Create a dashboard layout

Create a layout file for your dashboard pages (e.g., `app/(dashboard)/layout.tsx`):
Create a layout file for your dashboard pages (for example, `app/(dashboard)/layout.tsx`):
Copy link
Member Author

@oliviertassinari oliviertassinari Nov 1, 2024 •
edited by bharatkashyap
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was reported in https://github.com/mui/toolpad/pull/4080/files#diff-8223eb12de217e7e039331fde50c24a9cb7cc57e87c6982b28dc268dad0080b4

SCR-20241101-tama

See PR description (mui/mui-public#226 (comment)) for why it didn't break the CI.


```tsx title="app/(dashboard)/layout.tsx"
import * as React from 'react';
Expand Down Expand Up @@ -261,7 +261,7 @@ To integrate Toolpad Core into your Next.js Pages Router app, follow these steps

### 1. Wrap your application with `AppProvider`

In your root layout file (e.g., `pages/_app.tsx`), wrap your application with the `AppProvider`:
In your root layout file (for example, `pages/_app.tsx`), wrap your application with the `AppProvider`:

```tsx title="pages/_app.tsx"
import * as React from 'react';
Expand Down Expand Up @@ -357,7 +357,7 @@ Document.getInitialProps = async (ctx: DocumentContext) => {

### 3. Add a dashboard page

Create a dashboard page (e.g., `pages/index.tsx`):
Create a dashboard page (for example, `pages/index.tsx`):

```tsx title="pages/index.tsx"
import * as React from 'react';
Expand Down
Loading