Fixing page_history

[cvvergara]

page history does not show and its based on main, because it has an error

@pgRouting/admins

Summary by CodeRabbit

• Bug Fixes
  • Fixed a syntax error in the documentation version history display, ensuring version information is shown correctly.

[coderabbitai]

Walkthrough

A syntax error in the JavaScript array of versioned documentation entries for the 'pgr_nodeNetwork' file was corrected. The fix involved adjusting the placement of a version string within the array, ensuring the entry is syntactically valid and consistent with other elements. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
doc/_static/page_history.js	Fixed a syntax error in the array of versioned documentation entries by correcting object and version string placement.

Suggested labels

Documentation

Suggested reviewers

• robe2

Poem

A bunny hopped through docs one night,
And found a comma out of sight.
With nimble paws, it set things right—
Arrays aligned, the code now tight.
Now docs can hop from page to page,
Thanks to a rabbit’s gentle sage!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e710859 and 4f1253b.

📒 Files selected for processing (1)

• doc/_static/page_history.js (1 hunks)

🧰 Additional context used

🪛 Biome (1.9.4)

doc/_static/page_history.js

[error] 212-212: expected : but instead found }

Remove }

(parse)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: documentation (en)

🔇 Additional comments (1)

doc/_static/page_history.js (1)

212-212: ⚠️ Potential issue

Fix the syntax error in the versioned documentation entry.

There's a syntax error in the array of versioned documentation entries for the 'pgr_nodeNetwork' file. The issue is an extra comma after the version number 3.8, which creates invalid JavaScript syntax. This is causing the page history feature to not display correctly.

Apply this diff to fix the syntax error:

-        { v: '2.3', n: 'src/topology/doc/pgr_nodeNetwork'} , 3.8,
+        { v: '2.3', n: 'src/topology/doc/pgr_nodeNetwork'} , 3.8

This matches the pattern used in other similar entries in the file (lines 220, 224, 228, and 265).

Likely an incorrect or invalid review comment.

🧰 Tools

🪛 Biome (1.9.4)

[error] 212-212: expected : but instead found }

Remove }

(parse)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.