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

Add support for line numbers in Markdown code fences #1381

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

coreyasmith
Copy link
Contributor

Older versions of Ghost (2 and earlier?) used to support line numbers in Markdown code fences by adding line-numbers after the language:

```ruby line-numbers
foo = "bar"
```

This would be rendered as:

<pre>
  <code class="line-numbers language-ruby">
  foo = "bar"
  </code>
</pre>

The Prism Line Numbers plugin would then render line numbers for that code block.

This pull request adds in a markdown-it plugin that I implemented called markdown-it-fence-line-numbers to restore this functionality to Ghost's Markdown cards.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@coreyasmith coreyasmith force-pushed the markdown-code-fence-line-numbers branch from 83e9ea2 to 1e99d12 Compare October 10, 2024 12:19
Copy link

coderabbitai bot commented Feb 18, 2025

Walkthrough

The pull request introduces a new function, fenceLineNumbers, that enhances the Markdown renderer by adding support for line numbers in fenced code blocks. The function examines the token's info string for the keyword "line-numbers" and, if present, appends the corresponding class attribute to the token. If the keyword is absent or improperly included, the default rendering route is maintained. Additionally, the selectRenderer function is updated to apply this enhancement specifically for Ghost versions 4.x and later. New test cases have been added to verify that the renderer correctly includes or omits the "line-numbers" class based on the markdown input. The tests also confirm that the functionality does not affect behavior in versions of Ghost prior to 4.x.

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Sorry, something went wrong.

Copy link

@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

🧹 Nitpick comments (1)
packages/kg-markdown-html-renderer/test/markdown-html-renderer.test.js (1)

27-77: Consider adding edge case tests.

While the current test coverage is good, consider adding tests for:

  • Multiple language attributes
  • Invalid line-numbers placement (as first word)
  • Empty info string

Example test cases:

it('handles multiple language attributes correctly', function () {
    const markdown = '```javascript experimental line-numbers\nconst foo = "bar";\n```';
    const result = renderer.render(markdown, {ghostVersion: '4.0'});
    result.should.containEql('class="line-numbers language-javascript"');
});

it('treats line-numbers as language when specified first', function () {
    const markdown = '```line-numbers javascript\nconst foo = "bar";\n```';
    const result = renderer.render(markdown, {ghostVersion: '4.0'});
    result.should.containEql('class="language-line-numbers"');
    result.should.not.containEql('language-javascript');
});

it('handles empty info string correctly', function () {
    const markdown = '```\nconst foo = "bar";\n```';
    const result = renderer.render(markdown, {ghostVersion: '4.0'});
    result.should.not.containEql('line-numbers');
});
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bffca2d and 16b6352.

📒 Files selected for processing (2)
  • packages/kg-markdown-html-renderer/lib/markdown-html-renderer.js (2 hunks)
  • packages/kg-markdown-html-renderer/test/markdown-html-renderer.test.js (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Node 22.13.1
  • GitHub Check: Node 20.11.1
🔇 Additional comments (4)
packages/kg-markdown-html-renderer/lib/markdown-html-renderer.js (2)

45-72: LGTM! The fenceLineNumbers function implementation is well-structured.

The implementation correctly handles:

  • Fallback to default behavior when no info string is present
  • Proper parsing of language and attributes
  • Validation of the line-numbers attribute position
  • Graceful addition of the class attribute

The code is properly attributed to its original source.


109-110: LGTM! The fenceLineNumbers plugin is correctly integrated.

The plugin is appropriately added only for Ghost versions 4.x and later, maintaining backward compatibility.

packages/kg-markdown-html-renderer/test/markdown-html-renderer.test.js (2)

27-46: LGTM! The test cases for Ghost v4.x are comprehensive.

The tests properly verify:

  • Presence of line-numbers class when specified
  • Correct combination with language class

68-77: LGTM! The test case for Ghost <4.x ensures backward compatibility.

The test verifies that line-numbers is not included for older Ghost versions, maintaining backward compatibility.

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.

None yet

1 participant