Fix #667 - handle illegal response DTO instantiation correctly

Src/Directory.Build.props

@@ -1,7 +1,7 @@
 <Project>
  <PropertyGroup>
 
- <Version>5.24.0.8-beta</Version>
+ <Version>5.24.0.9-beta</Version>
 
  <TargetFrameworks>net6.0;net7.0;net8.0</TargetFrameworks>
  <LangVersion>latest</LangVersion>

Src/Library/Endpoint/Endpoint.Properties.cs

@@ -86,16 +86,23 @@ public bool ResponseStarted
  }
 
  static readonly JsonObject _emptyObject = new();
- static readonly JsonArray _emptyArray = new();
+ static readonly JsonArray _emptyArray = [];
 
  TResponse InitResponseDto()
  {
  if (_isStringResponse) //otherwise strings are detected as IEnumerable of chars
  return default!;
 
- _response = JsonSerializer.Deserialize<TResponse>(
- _isCollectionResponse ? _emptyArray : _emptyObject,
- Cfg.SerOpts.Options)!;
+ try
+ {
+ _response = JsonSerializer.Deserialize<TResponse>(
+ _isCollectionResponse ? _emptyArray : _emptyObject,
+ Cfg.SerOpts.Options)!;
+ }
+ catch
+ {
+ //do nothing
+ }
 
  return _response is null
  ? throw new NotSupportedException(

Src/Library/changelog.md

@@ -110,6 +110,21 @@ There was a possible contention issue that could arise in and extremely niche ed
 
 </details>
 
+<details><summary>Correct exception not thrown when trying to instantiate response DTOs with required properties</summary>
+
+When the response DTO contains required properties like this:
+
+```csharp
+public class MyResponse
+{
+ public required string FullName { get; set; }
+}
+```
+
+If an attempt was made to utilize the auto response sending feature by setting properties of the `Response` object, a 400 validation error was being thrown instead of a 500 internal server error. It is now correctly throwing the `NotSupportedException` as it should, because FE cannot automatically instantiate objects that have required properties and the correct usage is for you to instantiate the object yourself and set it to the `Response` property, which is what the exception will now be instructing you to do.
+
+</details>
+
 ## Breaking Changes ⚠️
 
 <details><summary>The way multiple Swagger request examples are set has been changed</summary>