Allow specifying child class names

[theit8514]

Is your feature request related to a problem?

When generating classes from a JSON that has nested data, the root object gets generated with my defined class name, but any classes generated from properties of the root object are generated with just the property name.

Describe the feature you'd like

I would like to be able to provide a handler that can rewrite or prefix the generated class names.

What alternatives have you considered?

No response

Additional context

Input code:

var options = new Json2SharpOptions
{
    TargetLanguage = Language.CSharp,
    CSharpOptions = new Json2SharpCSharpOptions
    {
        IsSealed = false,
        TargetType = CSharpObjectType.Class,
        SerializationAttribute = CSharpSerializationAttribute.NewtonsoftJson
    }
};
var rawJson = """{"users":[{"id":"be37a82a5e052a0482e021183f68dd8c","username":"Test 1","time":1751653380834},{"id":"c474b6fe22761d8c640b657c399e5aad","username":"Test 2","time":1751653386295}]}""";
var code = Json2Sharp.Parse("MessagePresenceList", rawJson, options);
Console.WriteLine(code);

Output code:

      using Newtonsoft.Json;

      public class MessagePresenceList
      {
          [JsonProperty("users")]
          public required Users[] Users { get; init; }
      }

      public class Users
      {
          [JsonProperty("id")]
          public required string Id { get; init; }

          [JsonProperty("username")]
          public required string Username { get; init; }

          [JsonProperty("time")]
          public required long Time { get; init; }
      }

If the sub-classes are prefixed, expected output would be:

      using Newtonsoft.Json;

      public class MessagePresenceList
      {
          [JsonProperty("users")]
          public required MessagePresenceListUsers[] Users { get; init; }
      }

      public class MessagePresenceListUsers
      {
          [JsonProperty("id")]
          public required string Id { get; init; }

          [JsonProperty("username")]
          public required string Username { get; init; }

          [JsonProperty("time")]
          public required long Time { get; init; }
      }

[Kaoticz]

Interesting. I'm going with the handler approach, as it sounds more flexible and powerful to the user.
I'm curious about your use-case though. What situation warrants this feature that could not be solved with a simple rename from your IDE of choice?

[theit8514]

I had a process that was intercepting data from a websocket and converting that to JSON serialized classes. Some of the objects had lots of nested objects/arrays, so the generated classes were big and often conflicted (e.g. a 'container' from one message type might conflict with a 'container' from a different message type). Changing it later is fine, but it would be nice to be able to handle this at generation time.

When parsing some of these objects, I also ended up with duplicate classes inside the same object. For example, in this JSON object, a Lines class is created twice. Being able to name the classes, I could make the first one "Lines" and the second one "HeadquartersAddressLines".

{
  "startingLocation": {
    "lines": [
      { ... }
    ],
  },
  "headquarters": {
    "address": {
      "lines": [
        { ... }
      ],
    }
  }
}