[dotnet] Add back in a public parameterless constructor to HttpRequestData

[RenderMichael]

User description

…stData`

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Motivation and Context

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

Bug fix

---

Description

• Added a public parameterless constructor to HttpRequestData.

• Updated RequestId property to allow null values.

---

Changes walkthrough 📝

	Relevant files
Bug fix	HttpRequestData.cs Add parameterless constructor and nullable `RequestId`      dotnet/src/webdriver/HttpRequestData.cs Added a public parameterless constructor initializing default values. Changed RequestId property to nullable type. +11/-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:

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Null Reference The parameterless constructor initializes required properties with null values which could lead to NullReferenceException when these properties are accessed. Consider initializing with empty values instead. this.Method = null!; this.Url = null!; this.Headers = null!;

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	✅ Initialize collection to prevent nulls Suggestion Impact: The commit implements the suggestion by initializing Headers with a new Dictionary instance, but does it at the property level instead of in the constructor code diff: - public Dictionary<string, string> Headers { get; set; } + public Dictionary<string, string> Headers { get; set; } = new Dictionary<string, string>(); Initialize the Headers dictionary in the parameterless constructor to prevent NullReferenceException when adding headers. dotnet/src/webdriver/HttpRequestData.cs [34-39] public HttpRequestData() { this.Method = null!; this.Url = null!; - this.Headers = null!; + this.Headers = new Dictionary<string, string>(); } Apply this suggestion Suggestion importance[1-10]: 8 __ Why: Initializing Headers with null! could lead to NullReferenceException at runtime. Using a new Dictionary instance is a safer approach that prevents potential crashes.	Medium
General	✅ Use meaningful defaults over nulls Suggestion Impact: The commit addresses the same issue but takes a different approach by making properties nullable and initializing Headers with default value code diff: - public string Method { get; set; } + public string? Method { get; set; } /// <summary> /// Gets the URL of the HTTP request. /// </summary> - public string Url { get; set; } + public string? Url { get; set; } /// <summary> /// Gets the POST data of the HTTP request, if any. @@ -73,7 +70,7 @@ /// <summary> /// Gets the headers of the HTTP request. /// </summary> - public Dictionary<string, string> Headers { get; set; } + public Dictionary<string, string> Headers { get; set; } = new Dictionary<string, string>(); Avoid using null-forgiving operator (!) for required properties. Instead, initialize with meaningful default values. dotnet/src/webdriver/HttpRequestData.cs [34-39] public HttpRequestData() { - this.Method = null!; - this.Url = null!; - this.Headers = null!; + this.Method = "GET"; + this.Url = string.Empty; + this.Headers = new Dictionary<string, string>(); } Apply this suggestion Suggestion importance[1-10]: 7 __ Why: Using meaningful default values instead of null-forgiving operators improves code safety and clarity. The suggestion provides sensible defaults that better represent the initial state of an HTTP request.	Medium