From c93a9243a2430fa6dc0817d9935e967bcf03f897 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Mon, 10 Feb 2025 13:34:58 +0100 Subject: [PATCH] fix some accidental extra newlines in docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Fredrik Adelöw --- .../software-catalog/catalog-customization.md | 16 ++++------------ docs/tutorials/react-router-stable-migration.md | 8 ++------ 2 files changed, 6 insertions(+), 18 deletions(-) diff --git a/docs/features/software-catalog/catalog-customization.md b/docs/features/software-catalog/catalog-customization.md index c56f763a4e..e3065cf1e7 100644 --- a/docs/features/software-catalog/catalog-customization.md +++ b/docs/features/software-catalog/catalog-customization.md @@ -70,9 +70,7 @@ The columns you see in the `CatalogIndexPage` were selected to be a good startin Suppose we want to add a new User Email column to the `User` kind in the Catalog. We can do this by overriding the `columns` that we pass into the `CatalogIndexPage` component in our `App.tsx`. First, we need to match the entity kind that we want to override, and then define the columns to show: ```tsx title="packages/app/src/App.tsx" -{ - /* highlight-add-start */ -} +{/* prettier-ignore */ /* highlight-add-start */} const myColumnsFunc: CatalogTableColumnsFunc = entityListContext => { if (entityListContext.filters.kind?.value === 'user') { return [ @@ -84,9 +82,7 @@ const myColumnsFunc: CatalogTableColumnsFunc = entityListContext => { return CatalogTable.defaultColumnsFunc(entityListContext); }; -{ - /* highlight-add-end */ -} +{/* prettier-ignore */ /* highlight-add-end */} ``` Then, we can implement the `createUserEmailColumn` function and add it to the list of columns. `field` is used to access the data from the entity, while `render` lets us customize how we display the data: @@ -391,13 +387,9 @@ export const EntitySecurityTierPicker = () => { Now we can add the component to `CatalogIndexPage`: ```tsx title="packages/app/src/App.tsx" -{ - /* highlight-add-start */ -} +{/* prettier-ignore */ /* highlight-add-start */} import { DefaultFilters } from '@backstage/plugin-catalog-react'; -{ - /* highlight-add-end */ -} +{/* prettier-ignore */ /* highlight-add-end */} const routes = ( diff --git a/docs/tutorials/react-router-stable-migration.md b/docs/tutorials/react-router-stable-migration.md index 017f69ba4f..f4dcc33559 100644 --- a/docs/tutorials/react-router-stable-migration.md +++ b/docs/tutorials/react-router-stable-migration.md @@ -181,13 +181,9 @@ It's crucial that you update to `RequirePermission` at the same time as you upda When migrating over to React Router v6 stable, you might also see browser console warnings for the `Navigate` component. This will need to be wrapped up in a `Route` component with the `Navigate` component in the `element` prop. ```tsx -{ - /* highlight-remove-next-line */ -} +{/* prettier-ignore */ /* highlight-remove-next-line */} ; -{ - /* highlight-add-next-line */ -} +{/* prettier-ignore */ /* highlight-add-next-line */} } />; ```