[dotnet] [bidi] Make LogEntry as not nested

[nvborisenko]

User description

Motivation and Context

Contributes to #15407

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Enhancement, Tests

---

Description

• Refactored nested DTO types to standalone classes for better extensibility.

• Updated LogEntry and related types to standalone classes.

• Adjusted JSON serialization and deserialization logic for new class structure.

• Updated tests to align with refactored LogEntry structure.

---

Changes walkthrough 📝

	Relevant files
Enhancement	5 files BiDiJsonSerializerContext.cs Updated JSON serialization for refactored `LogEntry` types +3/-3      LogEntryConverter.cs Adjusted polymorphic converter for `LogEntry` refactor      +5/-5      BrowsingContextLogModule.cs Updated method signatures to use new `LogEntry` types        +2/-2      LogEntry.cs Refactored `Entry` and nested types to standalone `LogEntry` classes +7/-7      LogModule.cs Updated `LogModule` to use refactored `LogEntry` types      +2/-2
Tests	2 files LogTest.cs Updated tests to align with `LogEntry` refactor                    +6/-6      ScriptCommandsTest.cs Adjusted script command tests for `LogEntry` changes          +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 15407 - PR Code Verified Compliant requirements: Don't use nested DTO types in the .NET BiDi implementation Replace nested types with standalone classes for better extensibility Maintain the same functionality while improving the API design Requires further human verification: Ensure static factory methods and static singletons can be added in the future

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review File Naming The file was renamed from Entry.cs to LogEntry.cs, but the copyright header still references the old file name. This should be updated to match the new file name. // <copyright file="LogEntry.cs" company="Selenium Committers">

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Learned best practice	Use TryGetProperty to safely check for property existence before accessing JSON properties to prevent exceptions The code directly accesses the "type" property without checking if it exists first, which could throw a JsonException if the property is missing. Use TryGetProperty to safely check for the property's existence before accessing it. dotnet/src/webdriver/BiDi/Communication/Json/Converters/Polymorphic/LogEntryConverter.cs [34-39] -return jsonDocument.RootElement.GetProperty("type").ToString() switch +if (!jsonDocument.RootElement.TryGetProperty("type", out JsonElement typeElement)) + return null; + +return typeElement.ToString() switch { "console" => jsonDocument.Deserialize<ConsoleLogEntry>(options), "javascript" => jsonDocument.Deserialize<JavascriptLogEntry>(options), _ => null, }; Apply this suggestion Suggestion importance[1-10]: 6	Low
Update

[RenderMichael]

Looks good, one small future-proofing change