Improved bit resx translator logging configuration (#11785)

[ysmoradi]

closes #11785

Summary by CodeRabbit

• Chores
  • Enhanced internal logging infrastructure to support configuration-based settings.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The application's logging configuration now supports reading settings from the Bit.ResxTranslator.json configuration file. A logging configuration line was added to wire up the configuration section, enabling external logging control without code changes.

Changes

Cohort / File(s)	Summary
Logging Configuration src/ResxTranslator/Bit.ResxTranslator/Program.cs	Added loggingBuilder.AddConfiguration(configuration.GetSection("Logging")); to enable configuration-based logging settings from the application configuration file

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-line addition in one file
• Straightforward integration of built-in logging configuration
• No complex logic or behavioral changes to review

Poem

🐰 A hop, a skip, through config we peek,
Logging settings, no more mystique!
From JSON files our logs now spring,
Configuration makes debugging sing! ✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: improving logging configuration for the bit resx translator, which directly addresses the linked issue about reading logging settings from the configuration file.
Linked Issues check	✅ Passed	The code change adds logging configuration hookup by calling loggingBuilder.AddConfiguration(), which directly addresses issue #11785's requirement to read logging configuration from Bit.ResxTranslator.json.
Out of Scope Changes check	✅ Passed	The single code change (adding logging configuration hookup) is directly scoped to resolving the linked issue #11785 about reading logging configuration; no unrelated changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 11785-bit-resx-translator-doesnt-read-logging-configuration-from-bitresxtranslatorjson

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between f131c6f and c46c0d6.

📒 Files selected for processing (1)

• src/ResxTranslator/Bit.ResxTranslator/Program.cs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (csharp)