JSON to JSON for .NET (Core)?
-
I don't think this is a programming question... :) I'm currently porting a Java application to .NET Core. Everything is fine except one thing... The Java application uses bazaarvoice/jolt: JSON to JSON transformation library[^]. It's pretty neat, one JSON comes in and another JSON (with the same values, but a completely different structure) comes out. All configured using... JSON! I can't seem to find something similar for .NET. Anyone know of anything? And no, I'm not going to JSON -> XML -> XSLT -> XML -> JSON.
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
XSLT (nasty one)?
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
-
I don't think this is a programming question... :) I'm currently porting a Java application to .NET Core. Everything is fine except one thing... The Java application uses bazaarvoice/jolt: JSON to JSON transformation library[^]. It's pretty neat, one JSON comes in and another JSON (with the same values, but a completely different structure) comes out. All configured using... JSON! I can't seem to find something similar for .NET. Anyone know of anything? And no, I'm not going to JSON -> XML -> XSLT -> XML -> JSON.
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
I didn't know that library. As for me, if you use the NewtonSoft JSON library, then you can leverage the JLinq section which offers a fluent API close to the Linq. With that you can do practically everything. There's only a thing which does not come for free, but it's not hard to write by yourself. It's the path-mapping of the nodes. However, I'd prefer the "pull" approach: the path should represent the node to retrieve (from the source), and that should be specified in the transformation template. Good luck!
-
I don't think this is a programming question... :) I'm currently porting a Java application to .NET Core. Everything is fine except one thing... The Java application uses bazaarvoice/jolt: JSON to JSON transformation library[^]. It's pretty neat, one JSON comes in and another JSON (with the same values, but a completely different structure) comes out. All configured using... JSON! I can't seem to find something similar for .NET. Anyone know of anything? And no, I'm not going to JSON -> XML -> XSLT -> XML -> JSON.
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I didn't know that library. As for me, if you use the NewtonSoft JSON library, then you can leverage the JLinq section which offers a fluent API close to the Linq. With that you can do practically everything. There's only a thing which does not come for free, but it's not hard to write by yourself. It's the path-mapping of the nodes. However, I'd prefer the "pull" approach: the path should represent the node to retrieve (from the source), and that should be specified in the transformation template. Good luck!
-
XSLT (nasty one)?
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
Sander Rossel wrote:
And no, I'm not going to JSON -> XML -> XSLT -> XML -> JSON.
Kornfeld Eliyahu Peter wrote:
XSLT (nasty one)?
:doh: Thanks for the attempt though :laugh:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Sander Rossel wrote:
And no, I'm not going to JSON -> XML -> XSLT -> XML -> JSON.
Kornfeld Eliyahu Peter wrote:
XSLT (nasty one)?
:doh: Thanks for the attempt though :laugh:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
You missed the point... XSLT can parse JSON and can write JSON... So no XML in the middle... But such XSLT is looks more nasty than the usual...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
-
You missed the point... XSLT can parse JSON and can write JSON... So no XML in the middle... But such XSLT is looks more nasty than the usual...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
Kornfeld Eliyahu Peter wrote:
You missed the point
Yep, never knew XSLT could do that. I'll continue Googling for an alternative X| Thanks though :thumbsup:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I didn't know that library. As for me, if you use the NewtonSoft JSON library, then you can leverage the JLinq section which offers a fluent API close to the Linq. With that you can do practically everything. There's only a thing which does not come for free, but it's not hard to write by yourself. It's the path-mapping of the nodes. However, I'd prefer the "pull" approach: the path should represent the node to retrieve (from the source), and that should be specified in the transformation template. Good luck!
Moreover, you can write custom converters for it to provide different serialization approaches: [Custom JsonConverter](https://www.newtonsoft.com/json/help/html/CustomJsonConverter.htm)
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
I don't think this is a programming question... :) I'm currently porting a Java application to .NET Core. Everything is fine except one thing... The Java application uses bazaarvoice/jolt: JSON to JSON transformation library[^]. It's pretty neat, one JSON comes in and another JSON (with the same values, but a completely different structure) comes out. All configured using... JSON! I can't seem to find something similar for .NET. Anyone know of anything? And no, I'm not going to JSON -> XML -> XSLT -> XML -> JSON.
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
How about: GitHub - WorkMaze/JUST.net: JUST - JSON Under Simple Transformation (XSLT equivalent for JSON).[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
"These people looked deep within my soul and assigned me a number based on the order in which I joined" - Homer
-
How about: GitHub - WorkMaze/JUST.net: JUST - JSON Under Simple Transformation (XSLT equivalent for JSON).[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
That looks promising, thanks :thumbsup:
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
