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.

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

CH22466[sc-website] - Update Node, YARN, Gatsby, React and other dependencies, Update MDX syntax #1626

Merged
merged 4 commits into from
Jun 11, 2024

Conversation

rameziophobia
Copy link
Contributor

@rameziophobia rameziophobia commented Jun 5, 2024

Summary

Fixed a few syntax errors in the docs and made the docs conform with MDX v2 syntax required for sc-website. More details can be found in the sc-website PR

Basically MDX v2 does not support html syntax, html comments, using {} or <> without escaping them. more details

Pull Request checklist

  • [] Add/update test to cover these changes -- Not needed
  • Update documentation
  • [] Update CHANGELOG file -- Not needed

This change is Reviewable

Summary by CodeRabbit

  • Documentation
    • Updated the description of the component_name option in the view helpers API documentation to clarify React component types and renderer functions.
    • Corrected markup and improved link descriptions in the code-splitting.md file for better readability and clarity.
    • Fixed URL typos and corrected markup in the deferred-rendering.md file to address React rendering issues and update outdated links.

Copy link
Contributor

coderabbitai bot commented Jun 5, 2024

Walkthrough

The updates primarily focus on enhancing documentation clarity and fixing minor issues. Changes include refining descriptions of React components and renderer functions in the view helpers API, correcting markup and URLs in code-splitting and deferred-rendering guides, and improving link descriptions for better readability and accuracy.

Changes

File Change Summary
docs/api/view-helpers-api.md Updated the description of the component_name option to clarify React component types and renderer function details.
docs/javascript/code-splitting.md Corrected markup and link descriptions to address React rendering issues and clarify code splitting implementation.
docs/outdated/deferred-rendering.md Fixed URL typos, corrected client/server markup, and updated a URL in the React on Rails Pro section.

Poem

In docs we weave, with care and grace,
Clear paths for code in every space.
React components now defined,
Markup fixed, URLs aligned.
A smoother journey, through the lines,
For all who read, our work refines.
🌟✨


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 36f342c and 9914952.

Files selected for processing (3)
  • docs/api/view-helpers-api.md (1 hunks)
  • docs/javascript/code-splitting.md (2 hunks)
  • docs/outdated/deferred-rendering.md (3 hunks)
Additional context used
LanguageTool
docs/outdated/deferred-rendering.md

[uncategorized] ~10-~10: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...e webpack documentation: > For big web apps it’s not efficient to put all code into...


[misspelling] ~14-~14: Did you mean “you're” (short for ‘you are’)? (YOUR)
Context: ...fore it's able to render. If you do all your rendering on the client side, you don't...


[uncategorized] ~16-~16: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ...attempted to reuse markup in a container but the checksum was invalid. This generall...


[uncategorized] ~16-~16: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...expecting. React injected new markup to compensate which works but you have lost many of t...


[uncategorized] ~16-~16: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...ted new markup to compensate which works but you have lost many of the benefits of s...


[duplication] ~26-~26: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...erather thanReactDOM.render` if you are are server rendering. ## Server vs. Clien...

docs/api/view-helpers-api.md

[uncategorized] ~4-~4: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...ated in your app/assets/webpack folder and you have registered your components, yo...


[grammar] ~28-~28: “React” is a proper noun and needs to be capitalized. (A_GOOGLE)
Context: ... contains the properties to pass to the react object, or a JSON string. If you pass a...


[misspelling] ~32-~32: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’. (EN_A_VS_AN)
Context: ...ce the use of the default DIV tag to be a SPAN tag. - trace: set to true to...


[uncategorized] ~38-~38: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ... false. True will throw an error on the server side rendering. Your controller will have to...


[duplication] ~96-~96: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...r controller or view to see what values are are in the Rails Context. Pass true or fals...


[uncategorized] ~96-~96: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ... you want to see the server side or the client side rails_context. Typically, for computing...


[uncategorized] ~106-~106: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...nctions are not meant to be used on the server since there's no DOM on the server. Ins...

docs/javascript/code-splitting.md

[misspelling] ~15-~15: Did you mean “you're” (short for ‘you are’)? (YOUR)
Context: ...fore it's able to render. If you do all your rendering on the client side, you don't...


[uncategorized] ~17-~17: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ...attempted to reuse markup in a container but the checksum was invalid. This generall...


[uncategorized] ~17-~17: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE)
Context: ...ted new markup to compensate which works but you have lost many of the benefits of s...


[style] ~23-~23: Consider removing “of” to be more concise (ALL_OF_THE)
Context: ...server. This means that react will tear all of the server rendered code out of the DOM, an...


[duplication] ~27-~27: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...erather thanReactDOM.render` if you are are server rendering. Here's an example of...


[style] ~109-~109: This phrase is redundant. Consider using “inside”. (OUTSIDE_OF)
Context: ...ete render. Then we do the first render inside of the callback, so that the first render ...


[style] ~134-~134: Consider using “incapable” to avoid wordiness. (NOT_ABLE_PREMIUM)
Context: ... server rendering with ExecJS, which is not capable of doing anything asynchronous. It woul...


[grammar] ~150-~150: “React” is a proper noun and needs to be capitalized. (A_GOOGLE)
Context: ...with /assets/ in the request url. The react on rails sets up the webpack config to ...

Markdownlint
docs/outdated/deferred-rendering.md

28-28: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


35-35: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


36-36: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


17-17: null (MD028, no-blanks-blockquote)
Blank line inside blockquote


19-19: null (MD028, no-blanks-blockquote)
Blank line inside blockquote

docs/api/view-helpers-api.md

1-1: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


2-2: Expected: 1; Actual: 0; Above (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


81-81: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


131-131: null (MD025, single-title, single-h1)
Multiple top-level headings in the same document


18-18: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


91-91: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


40-40: Expected: ------------; Actual: ------------- (MD035, hr-style)
Horizontal rule style


18-18: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified

docs/javascript/code-splitting.md

31-31: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


38-38: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


55-55: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


72-72: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


18-18: null (MD028, no-blanks-blockquote)
Blank line inside blockquote


20-20: null (MD028, no-blanks-blockquote)
Blank line inside blockquote


32-32: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


39-39: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


56-56: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


69-69: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


73-73: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


156-156: null (MD034, no-bare-urls)
Bare URL used

Additional comments not posted (5)
docs/outdated/deferred-rendering.md (3)

18-18: Corrected the comment syntax for MDX v2 compatibility.


20-20: Updated the server-side rendering syntax to be compatible with MDX v2.


37-37: Fixed the URL to ensure it is correctly formatted and accessible.

docs/api/view-helpers-api.md (1)

25-25: Expanded the definition of component_name to include "renderer function" and detailed its usage, enhancing clarity and utility for developers.

docs/javascript/code-splitting.md (1)

121-121: Updated the link description to clarify where code splitting is implemented, improving documentation accuracy and user guidance.

@justin808 justin808 merged commit 9c262c1 into master Jun 11, 2024
16 checks passed
@justin808 justin808 deleted the ramezweissa/doc-updates branch June 11, 2024 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants