Mimic mdBook implementation 🎁

[CoralPink]

Switch from lazy_static::lazy_static to once_cell::sync::lazy
And, it includes the fix for #78.

(I don't know why, but I can't pass the #78 check, so I will merge it through this PR just to be safe...)

Summary by CodeRabbit

• Refactor
  • Improved footnote processing initialization for enhanced performance and maintainability.

[coderabbitai]

Warning

Rate Limit Exceeded

@CoralPink has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 21 minutes and 31 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 113519d and 19bc626.

Walkthrough

The mdbook-footnote module has been refined to utilize the once_cell crate for more efficient lazy initialization. The switch from lazy_static to once_cell involves a change in how the FOOTNOTE_RE regular expression is instantiated, streamlining the initialization process within the module.

Changes

File(s)	Summary
rs/mdbook-footnote/src/lib.rs	Replaced lazy_static with once_cell::sync::Lazy for initializing FOOTNOTE_RE.

Poem

🐇
In the land of code, where the snippets roam free,
A change was made, as easy as can be.
From lazy_static to once_cell we hop,
For lazy init, we're now at the top! 🚀
🐇

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 145a679 and 113519d.

Files ignored due to path filters (2)

• rs/mdbook-footnote/Cargo.lock is excluded by: !**/*.lock
• rs/mdbook-footnote/Cargo.toml is excluded by: !**/*.toml

Files selected for processing (1)

• rs/mdbook-footnote/src/lib.rs (2 hunks)

Additional comments: 2

rs/mdbook-footnote/src/lib.rs (2)

• 5-6: The change from lazy_static to once_cell::sync::Lazy for FOOTNOTE_RE is correctly implemented.
• 37-42: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [9-39]

The logic within the replacing function appears to be correct and uses the FOOTNOTE_RE regex as intended. Ensure that the changes to the regex initialization do not affect the behavior of this function.

[CoralPink]

Thanks for pointing that out! 🥕

Okay, merge!