8000 TimeSource - Updated XML docs with Wiki-links by snakefoot · Pull Request #5901 · NLog/NLog · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

TimeSource - Updated XML docs with Wiki-links #5901

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

Merged
merged 1 commit into from
Jun 24, 2025

Conversation

snakefoot
Copy link
Contributor

No description provided.

Copy link
coderabbitai bot commented Jun 24, 2025

Walkthrough

XML documentation remarks and "seealso" tags referencing the NLog Wiki page about Time Source were added to several time source classes. These changes enhance the inline documentation without altering any class functionality, method signatures, logic, or control flow.

Changes

File(s) Change Summary
src/NLog/Time/AccurateLocalTimeSource.cs Added XML documentation remarks and "seealso" tag linking to NLog Wiki for AccurateLocalTimeSource.
src/NLog/Time/AccurateUtcTimeSource.cs Added XML documentation remarks and "seealso" tag linking to NLog Wiki for AccurateUtcTimeSource.
src/NLog/Time/CachedTimeSource.cs Added XML documentation remarks and "seealso" tag linking to NLog Wiki for CachedTimeSource.
src/NLog/Time/FastLocalTimeSource.cs Added XML documentation remarks and "seealso" tag linking to NLog Wiki for FastLocalTimeSource.
src/NLog/Time/FastUtcTimeSource.cs Added XML documentation remarks and "seealso" tag linking to NLog Wiki for FastUtcTimeSource.
src/NLog/Time/TimeSource.cs Added XML documentation remarks and "seealso" tag linking to NLog Wiki for TimeSource abstract class.

Poem

In the warren of code, the docs now gleam,
With links to the Wiki, a developer’s dream.
Time sources explained, with remarks so clear,
Rabbits rejoice, for guidance is near!
🐇✨


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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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 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.

@snakefoot snakefoot enabled auto-merge (squash) June 24, 2025 19:01
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 (6)
src/NLog/Time/TimeSource.cs (1)

43-46: Replace raw <a> tag with <see href> and drop the redundant <seealso>

<a> isn’t recognised by the C# XML–doc tool-chain and can surface CS15xx warnings.
Using <see href> is the recommended way to embed external links and renders correctly in IntelliSense / doc generators. The <seealso> that follows points to the exact same URL, so one link is enough.

-    /// <a href="https://github.com/NLog/NLog/wiki/Time-Source">See NLog Wiki</a>
-    /// </remarks>
-    /// <seealso href="https://github.com/NLog/NLog/wiki/Time-Source">Documentation on NLog Wiki</seealso>
+    /// <see href="https://github.com/NLog/NLog/wiki/Time-Source">NLog Wiki – Time Source</see>
+    /// </remarks>

Run a quick build or grep for <a href= to confirm the repo stays warning-free.

src/NLog/Time/FastUtcTimeSource.cs (1)

41-44: Use <see href> instead of raw <a> and avoid duplicate link

Same rationale as for TimeSource.cs: avoid potential XML-doc warnings and keep a single canonical link.

-    /// <a href="https://github.com/NLog/NLog/wiki/Time-Source">See NLog Wiki</a>
-    /// </remarks>
-    /// <seealso href="https://github.com/NLog/NLog/wiki/Time-Source">Documentation on NLog Wiki</seealso>
+    /// <see href="https://github.com/NLog/NLog/wiki/Time-Source">NLog Wiki – Time Source</see>
+    /// </remarks>
src/NLog/Time/FastLocalTimeSource.cs (1)

41-44: Align with XML-doc best practice

Swap <a> for <see href> and drop the second link for the same reasons stated earlier.

-    /// <a href="https://github.com/NLog/NLog/wiki/Time-Source">See NLog Wiki</a>
-    /// </remarks>
-    /// <seealso href="https://github.com/NLog/NLog/wiki/Time-Source">Documentation on NLog Wiki</seealso>
+    /// <see href="https://github.com/NLog/NLog/wiki/Time-Source">NLog Wiki – Time Source</see>
+    /// </remarks>
src/NLog/Time/AccurateUtcTimeSource.cs (1)

41-44: Consistent hyperlink markup

Recommend the same <see href> swap and removal of the duplicate <seealso>.

-    /// <a href="https://github.com/NLog/NLog/wiki/Time-Source">See NLog Wiki</a>
-    /// </remarks>
-    /// <seealso href="https://github.com/NLog/NLog/wiki/Time-Source">Documentation on NLog Wiki</seealso>
+    /// <see href="https://github.com/NLog/NLog/wiki/Time-Source">NLog Wiki – Time Source</see>
+    /// </remarks>
src/NLog/Time/CachedTimeSource.cs (1)

41-44: Tidy up XML documentation link

For uniformity across the codebase, switch to <see href> and remove the extra <seealso>.

-    /// <a href="https://github.com/NLog/NLog/wiki/Time-Source">See NLog Wiki</a>
-    /// </remarks>
-    /// <seealso href="https://github.com/NLog/NLog/wiki/Time-Source">Documentation on NLog Wiki</seealso>
+    /// <see href="https://github.com/NLog/NLog/wiki/Time-Source">NLog Wiki – Time Source</see>
+    /// </remarks>
src/NLog/Time/AccurateLocalTimeSource.cs (1)

41-44: Prefer <see href="…"> over raw <a> to stay XML-doc compliant and avoid duplicate links

Raw HTML anchors aren’t interpreted by most XML-doc toolchains (IntelliSense, DocFX, etc.) and will render as plain text or trigger warnings, whereas <see> / <seealso> are first-class.
You already expose the same URL via <seealso>, so the anchor in <remarks> is redundant.

-/// <remarks>
-/// <a href="https://github.com/NLog/NLog/wiki/Time-Source">See NLog Wiki</a>
-/// </remarks>
+/// <remarks>
+/// <see href="https://github.com/NLog/NLog/wiki/Time-Source">NLog Wiki – Time Source</see>
+/// </remarks>

This keeps the docs cleaner and compiler-friendly.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bec94cb and 70906d2.

📒 Files selected for processing (6)
  • src/NLog/Time/AccurateLocalTimeSource.cs (1 hunks)
  • src/NLog/Time/AccurateUtcTimeSource.cs (1 hunks)
  • src/NLog/Time/CachedTimeSource.cs (1 hunks)
  • src/NLog/Time/FastLocalTimeSource.cs (1 hunks)
  • src/NLog/Time/FastUtcTimeSource.cs (1 hunks)
  • src/NLog/Time/TimeSource.cs (1 hunks)

Copy link

@snakefoot snakefoot merged commit 23f7421 into NLog:dev Jun 24, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0