Reason for everything could be undefined?

[fredrikj31]

Hi.

I have been working with different JS sdk's for a while now, and I write all my programs in TypeScript, and therefore I have one question about the the types.

Is there a obvious reason why every property in every sdk could be undefined and not just string or a type? It's pretty annoying to make my own types every time for the sdk, or typecheck every property.

So are there a good reason, or is it just the way it got built?

Best regards Fredrik Johansen.

[RanVaknin]

Hi @fredrikj31 ,

I'm not entirely sure what you mean by you "making your own types"

Can you share an example so I could better understand the problem at hand?

Thanks,
Ran

[fredrikj31]

By "making my own types" I mean, like overwrite the already built in types.

An example could be that when we create a MediaLive channel with a specific name, then the name would exists and therfore could not be undefined, as the sdk says.

Many of the properties which the sdk returns does not make sense, that it could both be a string and undefined, when it's obvious that some of the properties would be there every time.

The screenshot is from the "MediaPackage" sdk

Thanks for the support.
Fredrik Johansen

[RanVaknin]

@fredrikj31

Please refer to @trivikr 's comment here laying out the design decision.

Thanks,
Ran

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.