Mark generated code as generated to avoid analyzers working on it

[Yusyuriv]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes update the source generator by introducing a new constant string holding the generator's name and a variable that retrieves its assembly version. These values are used to append a generated code attribute to the output of the GenerateClass method in the source generator. The method's flow remains the same aside from these additional lines.

Changes

File Path	Change Summary
Flow.Launcher.Localization.SourceGenerators/.../LocalizeSourceGenerator.cs	Added a constant name for the generator's name and a variable version from the assembly. Appended [System.CodeDom.Compiler.GeneratedCode("{name}", "{version}")] to the generated code in GenerateClass.

Sequence Diagram(s)

sequenceDiagram
    participant C as Caller
    participant G as GenerateClass
    participant SB as StringBuilder

    C->>G: Invoke GenerateClass()
    G->>G: Define constant 'name'
    G->>G: Retrieve assembly version into 'version'
    G->>SB: Append GeneratedCode attribute with name & version
    G->>G: Continue with class generation
    G->>C: Return generated code

Loading

Poem

I'm a rabbit with a joyful beat,
Hopping through code with a rhythmic tweet.
I sniff out constants and version clues,
Decorating classes with a generated muse.
Leaping forward in code, oh what a treat!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0995c9b and 0c6d3dd.

📒 Files selected for processing (1)

• Flow.Launcher.Localization.SourceGenerators/Localize/LocalizeSourceGenerator.cs (1 hunks)

🔇 Additional comments (1)

Flow.Launcher.Localization.SourceGenerators/Localize/LocalizeSourceGenerator.cs (1)

308-311: Excellent improvement for ignoring generated code in analyzers.

The added code properly marks the generated class with [System.CodeDom.Compiler.GeneratedCode] attribute, which will help code analysis tools recognize that this code is auto-generated and should be excluded from analysis. This is a best practice for source generators as it reduces noise in code analysis results and prevents false positives.

The implementation correctly:

1. Uses nameof for the generator name (good for refactoring)
2. Retrieves the version from the assembly
3. Adds the attribute with both parameters

✨ 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.

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