Fix column layout in documentation of Modelica.Media.IdealGases.SingleGases

[LeoSchmider]

Edited documentation from Modelica.Media.IdealGases.SingleGases.mo

Summary by CodeRabbit

• Documentation
  • Enhanced the clarity of chemical names in documentation by splitting merged entries into distinct components, improving readability and accuracy.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

The changes modify the documentation in the Modelica/Media/IdealGases/SingleGases.mo file. The update splits compound gas names into separate entries—specifically separating "Nitrous Oxide" into "Nitrous" and "Oxide" and "Neon Oxygen" into "Neon" and "Oxygen". No functional or public entity alterations have been made.

Changes

File	Change Summary
Modelica/Media/IdealGases/SingleGases.mo	Updated documentation formatting: separated "Nitrous Oxide" into "Nitrous" and "Oxide", and "Neon Oxygen" into "Neon" and "Oxygen".

Poem

I'm a rabbit, hopping through the code,
Splitting names down the winding road.
Nitrous and Oxide, now clear to see,
Neon and Oxygen, running wild and free.
With a twitch of joy and an ASCII hop,
The docs now shine—coding won't stop!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Modelica/Media/IdealGases/SingleGases.mo (1)

366-366: Documentation Table Formatting Improvement

The revised preformatted gas list on line 366 now clearly separates entries so that “Neon” and “Oxygen” are distinct, enhancing readability. Please verify that the change correctly reflects the intended “fix” for compound names—if the goal was also to split “Nitrous Oxide” into “Nitrous” and “Oxide,” double-check that the formatting and spacing convey that clearly and that the total number of gases remains consistent with the expected 37.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e99301b and 149459e.

📒 Files selected for processing (1)

• Modelica/Media/IdealGases/SingleGases.mo (1 hunks)

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

• GitHub Check: external_c_checks_cmake_windows-msvc
• GitHub Check: external_c_checks_cmake_windows-cygwin

[Esther-Devakirubai]

Backported to maint/4.1.x by #4625