JSON from DB to TS object

[sleek sand]

https://angular.io/guide/http#requesting-a-typed-response

[fast star]

Im requesting big object\

this is just a part of it

if i wouldnt, i would just map it somehow

[fierce sage]

The advantage of using js/ts is that each object has the same structure as json. Therefore create an interface with the property REG_TITLE_COMMENT like this

export interface MyData {
    REG_TITLE_COMMENT: string
    OtherProperty: string
    ...
}

[fast star]

This is full object 😄

[fierce sage]

If youre using the http client stick to the doc that jbnizet sent

[sleek sand]

So what? What does it change if the object is big or not? The solution is always the same: define an interface describing your object structure, and use it.

[acoustic garden]

Do you actually care about just one of its properties?

[fast star]

No it can be changed manually

added or removed

Threre can be multiple options and I need to take all, put them into some object and use them as needed

String of JSON is stored in
Object.nastavenia.textyJsonSk - this object I need to parse somehow

.\"}",

        "textyJsonEn": "{\"REG_TITLE_COMMENT\":\"Due to full capacity, accommodation is no longer possible. In case of interest, the participant can provide their own accommodation and meals, for example in a nearby guest house located 500 meters from the conference venue (the conference fee is reduced). Please contact us if you will require the help with accommodation near the conference venue \"}"
    },

[acoustic garden]

I don't know how this object with REG_TITLE_COMMENT relates with the big one you showed earlier.

[fast star]

im having big object about settings

and there inside it is another object i need

and there is that one I showed you before your message

[sleek sand]

interface Something {
  navastenia: {
    textyJsonSk: string;
  }
}
interface JsonThing {
  REG_TITLE_COMMENT: string;
}

const result$: Observable<JsonThing> = http.get<Something>(url).pipe(
  map(something => JSON.parse(something.navastenia.textyJsonSk))
);

[acoustic garden]

That's why I asked if you care about just that property or not.

[fast star]

i dont

[acoustic garden]

So you need to define interfaces for all the possible properties of that object, and in turn for all the object nested inside it, or inside its arrays.

[fast star]

yes and than map it as jbiznet showed?

[acoustic garden]

If you define all the interfaces you don't need to parse by JSON

[sleek sand]

Well, if you care about other properties, you probably won't map, no. But you will still get a Something, then access the property you asked about and use JSON.parse() to parse it as a JsonThing.

[sleek sand]

Yes, he does, because he has an JSON string stored inside a property of the main JSON.