chore: upgrade to docusarus v3 #1914
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
lennessyy
commented
Dec 18, 2023
| @@ -49,7 +49,7 @@ export default function CodeBlockString({ | |||
| > | |||
| {title && <div className={styles.codeBlockTitle}>{title}</div>} | |||
| <div className={styles.codeBlockContent}> | |||
| <Highlight {...defaultProps} theme={prismTheme} code={code} language={language ?? "text"}> | |||
There was a problem hiding this comment.
I investigated this one. defaultProps is not being exported anymore. The old defaultProps.js file just has the following content:
import Prism from "prism-react-renderer/prism";
import theme from "prism-react-renderer/themes/duotoneDark"; // Adjust the theme import based on availability
<Highlight Prism={Prism} theme={theme} code={code} language={language ?? "text"}>
{/* rest of your component code */}
</Highlight>
I haven't found this to really do anything? so I simply removed it.
| @@ -9,7 +9,7 @@ import { | |||
| } from "@docusaurus/theme-common"; | |||
| import { | |||
| isActiveSidebarItem, | |||
| findFirstCategoryLink, | |||
There was a problem hiding this comment.
This function is no longer being exported. I think the replacement covers the functionality of the old function.
karl-cardenas-coding
added
enhancement
lennessyy
requested review from
karl-cardenas-coding,
yuliiiah and
caroldelwing
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…rium into docusaurus-v3
| | `before-reset` | This stage executes before reset. | | | ||
| | Stage | Description | | ||
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'rootfs'?
| | `before-reset` | This stage executes before reset. | | | ||
| | Stage | Description | | ||
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'initrd'?
| | `before-reset` | This stage executes before reset. | | | ||
| | Stage | Description | | ||
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'chroot'?
| | Stage | Description | | ||
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | | ||
| | `initramfs` | This is still an early stage, running before switching to root. Here you can apply changes to the booting setup of Elemental. Despite executing this before switching to root, this invocation is chrooted into the target root after the immutable rootfs is set up and ready. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'chrooted'?
| | Stage | Description | | ||
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | | ||
| | `initramfs` | This is still an early stage, running before switching to root. Here you can apply changes to the booting setup of Elemental. Despite executing this before switching to root, this invocation is chrooted into the target root after the immutable rootfs is set up and ready. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'rootfs'?
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | | ||
| | `initramfs` | This is still an early stage, running before switching to root. Here you can apply changes to the booting setup of Elemental. Despite executing this before switching to root, this invocation is chrooted into the target root after the immutable rootfs is set up and ready. | | ||
| | `boot` | This stage executes after initramfs has switched to root and during the systemd boot-up process. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'initramfs'?
| | ---- | ---- | | ||
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | | ||
| | `initramfs` | This is still an early stage, running before switching to root. Here you can apply changes to the booting setup of Elemental. Despite executing this before switching to root, this invocation is chrooted into the target root after the immutable rootfs is set up and ready. | | ||
| | `boot` | This stage executes after initramfs has switched to root and during the systemd boot-up process. | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'systemd'?
| | `rootfs` | This is the earliest stage, running before switching to root. It happens right after the root is mounted in /sysroot and before applying the immutable rootfs configuration. This stage is executed over initrd root, no chroot is applied. | | ||
| | `initramfs` | This is still an early stage, running before switching to root. Here you can apply changes to the booting setup of Elemental. Despite executing this before switching to root, this invocation is chrooted into the target root after the immutable rootfs is set up and ready. | | ||
| | `boot` | This stage executes after initramfs has switched to root and during the systemd boot-up process. | | ||
| | `fs` | This stage is executed when fs is mounted and is guaranteed to have access to the state and persistent partitions ( COS_STATE and COS_PERSISTENT respectively). | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'fs'?
| | `after-install` | This stage executes after the installation of the OS. | | ||
| | `after-install-chroot` | This stage executes after the installation of the OS ends. | | ||
| | `after-upgrade` | This stage executes after the OS upgrade ends. | | ||
| | `after-upgrade-chroot` | This stage executes after the OS upgrade ends (chroot call). | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'chroot'?
| | `after-upgrade` | This stage executes after the OS upgrade ends. | | ||
| | `after-upgrade-chroot` | This stage executes after the OS upgrade ends (chroot call). | | ||
| | `after-reset` | This stage executes after the OS resets. | | ||
| | `after-reset-chroot` | This stage executes after the OS resets (chroot call). | |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'chroot'?
|
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 4.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the Change
This PR upgrades the docusaurus version used by the site to docusaurus v3.0.1
Review Changes
💻 Add Preview URL
🎫 Jira Ticket