-
Notifications
You must be signed in to change notification settings - Fork 199
docs: apply minor improvements #647
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
Conversation
Getting Started - remove the mxGraph copyright because the content does not include the mxGraph documentation (this was the case when the page was created, but no longer). - order package manager alphabetically - better lint comment about parent CSS: import and configuration in bundlers
WalkthroughThe pull request focuses on improving documentation for the Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (2)
packages/website/docs/usage/css-and-images.md (1)
40-50: LGTM! Consider adding a note about CSS modules.The new section provides clear and accurate guidance about CSS configuration in build tools. The examples and references are helpful.
Consider adding a note about CSS modules support, as it's a common approach in modern web applications. For example:
Some manage this automatically, like [Vite](https://vite.dev/), others require specific plugins. See the documentation of your build tool or framework for more information. + +Note: If you're using CSS Modules, you'll need to configure your build tool accordingly. The default CSS file can be imported as a global stylesheet.README.md (1)
57-60: Add language specification to the code block.The code block is missing a language specification, which is flagged by markdownlint.
Apply this diff to fix the markdown formatting:
yarn -``` +```bash yarn add @maxgraph/core<details> <summary>🧰 Tools</summary> <details> <summary>🪛 Markdownlint (0.37.0)</summary> 58-58: null Fenced code blocks should have a language specified (MD040, fenced-code-language) </details> </details> </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: CodeRabbit UI** **Review profile: CHILL** **Plan: Pro** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 977fd0d96b3bb880d85ff8824d51015c719b33cd and e0d8e607de61592d423d9ee33453ea8005ad165b. </details> <details> <summary>📒 Files selected for processing (3)</summary> * `README.md` (2 hunks) * `packages/website/docs/getting-started.mdx` (4 hunks) * `packages/website/docs/usage/css-and-images.md` (1 hunks) </details> <details> <summary>🧰 Additional context used</summary> <details> <summary>🪛 Markdownlint (0.37.0)</summary> <details> <summary>README.md</summary> 58-58: null Fenced code blocks should have a language specified (MD040, fenced-code-language) </details> </details> </details> <details> <summary>⏰ Context from checks skipped due to timeout of 90000ms (1)</summary> * GitHub Check: build </details> <details> <summary>🔇 Additional comments (4)</summary><blockquote> <details> <summary>packages/website/docs/getting-started.mdx (3)</summary> `16-16`: **LGTM! Clear and concise versioning information.** The simplified versioning description with a link to semver.org is more maintainable and provides better context. --- `35-39`: **LGTM! Package managers are now alphabetically ordered.** The reordering of package managers (npm, pnpm, yarn) improves the documentation's organization. --- `70-71`: **LGTM! Enhanced comment clarity.** The comment about the default parent is now more readable with proper line breaks. </details> <details> <summary>README.md (1)</summary> `83-84`: **LGTM! Enhanced comment readability.** The comment about the default parent is now more readable with proper line breaks. </details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
Getting Started
the page was created, but no longer).
CSS: import and configuration in bundlers
Summary by CodeRabbit
Documentation
yarnChores