Add ability to convert BinaryData into a dictionary or a dynamic type
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- backend-api-design
Research direction
Start by reviewing the existing BinaryData API and the JsonNode workaround described in the issue, then compare the linked Azure extension methods. Done means BinaryData can expose data under a JSON property for conversion to a typed collection, dictionary, or dynamic representation, with the supported API shape established.
Written by the indexing model from the issue text.
Description
There are cases where you are dealing with a BinaryData instance which contains some data following a known JSON schema under a given property, e.g.
{
"pets": [
{
"id": 1,
"name": "Buddy",
"type": "Dog",
"age": 5
},
{
"id": 2,
"name": "Mittens",
"type": "Cat",
"age": 3
}
],
"next": "https://api.example.com/pets?page=2"
}
I want to deserialize everything under "pets" into a List<Pet>. There isn't a simple way to do this with the BinaryData API. In Azure, there is an extension method that allows you converting BinaryData to a dynamic type. There is also another extension method that allows converting to a dictionary of string, object here. Having this ability outside of Azure would be helpful.
Ultimately, I'd like to be able to do this:
List<Pet> pets = binaryData["pets"].ToObjectFromJson<List<Pet>>();
or how it would look with the Azure extension method:
List<Pet> pets = binaryData.ToDynamicFromJson().Pets.ToObjectFromJson<List<Pet>>();
As a workaround, I was able to use JsonNode, but it feels like there is something missing from the BinaryData API:
var node = JsonNode.Parse(page.GetRawResponse().Content.ToString())!;
List<Pet> pets = node["pets"].ToObjectFromJson<List<Pet>>();
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·