Question 248012 in Json Question posted in
Our archive of expertly curated questions and answers provides insights and solutions to common problems related to this popular data interchange format. From parsing and manipulating JSON data to integrating it with various programming languages and web services, our archive has got you covered. Start exploring today and take your JSON skills to the next level

.NET 6 Service: how to pass JSON inside JSON?

I am developing a .NET 6 web service (with Startup), one of methods is

public async Task<ActionResult> PutDirector([FromBody] Director director, CancellationToken cancellationToken)
{
    var title = nameof(PutDirector);
    // ....
}

Using Swagger I pass this JSON:

{
  "id": 2,
  "firstName": "Yeh",
  "lastName": "Dobedo",
  "title": "Mr",
  "birthDate": "1983-09-18",
  "address": "15 Book Street",
  "search_Permission": true
}

It works fine.

By design I need to store json in the field address, i.e. a client app will parse and process this sub-json.

But when I pass

{
  "id": 2,
  "firstName": "Yeh",
  "lastName": "Dobedo",
  "title": "Mr",
  "birthDate": "1983-09-18",
  "address": "[
      {
        'line1': '15 Book Street',
        'line2': '21 Book Street'
      }
    ],",
  "search_Permission": true
}

the method in the controller receives Director object == null.

I understand that JSON cannot be deserialized to object. How to pass JSON where string contains json?

Tags:

2

Answers


  1. 0

    your json is not valid, if you want to treat an address object as a string, you need this json

    {
  "id": 2,
  "firstName": "Yeh",
  "lastName": "Dobedo",
  "title": "Mr",
  "birthDate": "1983-09-18",
   "address": "[
       {
        "line1": "15 Book Street",
        "line2": "21 Book Street"
      }
    ]",
  "search_Permission": true
}

    or a string as an object ( remove extra "")

    "address": [
      {
        'line1': '15 Book Street',
        'line2': '21 Book Street'
      }
    ],

    but I would advice to create a json custom converter

    Login or Signup to reply.
  2. 0

    While I prefer @Serge’s answer above, I wanted to point out another option for dealing with strings that are sometimes very difficult to use escape codes on.

    For this to work, the client side has to understand what it is receiving. Most of the time, this means that you are writing both the service and the client code.

    Difficult to escape strings can be converted to a non json strings. There are a lot of ways to do this, but a 64 bit string is pretty easy.

    To encode a string named addressJson:

    // serialize to json string stored in addressJson first

// convert to base 64 string
string jsonSafe = Convert.ToBase64String(addressJson);

    The encoded string (your address json from above) looks like this:
    WwogICAgICAgewogICAgICAgIFwibGluZTFcIjogXCIxNSBCb29rIFN0cmVldFwiLAogICAgICAgIFwibGluZTJcIjogXCIyMSBCb29rIFN0cmVldFwiCiAgICAgIH0KICAgIF0=

    To decode on the client side:

    // convert base 64 string back into your json
string addressJson = Encoding.UTF8.GetString(Convert.FromBase64String(base64EncodedData));

// then send addressJson to your json deserializer to get the address object

    Its a little more tricky to decode because the string encoding isnt assumed, but, as you can see above, it’s still pretty easy.

    The downside to this method is that the data in your json is not easily human readable anymore, but this may or may not matter to you.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search