When to use Struct?

[peerreynders]

[quote=“arashm, post:5, topic:2396”]
One of them has name attribute and the other title but with same value and purpose.[/quote]

@arashm

So I thought I’d convert those JSON data to different structs and define a to_normalized_struct function in those to convert them to a struct that provides a same interface to be used through out the app.

I would lean towards parsing the data in both cases into a generic Map and then generating the normalized structure from the data in the Map. I’d basically end up with 3 modules, one for the normalized struct, one for the product collection conversion and one for the single product conversion - possibly a fourth for commonalities between the last two - depends on how (in)consistent they are.

@bbense

Each flow or path through the application will likely require it’s own unique data structure;

Though not necessary, I would typically expect more than one data structure/shape per flow. As the data moves through the transformation pipeline the shape tends to pick up derived/looked up details that drive towards the desired end result.