[Feature] Add width & height to media detail model

[Dvergar]

This PR adds width & height to the model returned by the connector detail method. MediaDetail model is now diverging from Media (query method).

Related tickets

https://chilipublishintranet.atlassian.net/browse/EDT-1054

[github-actions]

Coverage report can be checked at https://chili-dev.azureedge.net/sdk/coverage/361/coverage.html

[github-actions]

Unit Test Results

    1 files    31 suites   24s ⏱️
284 tests 284 ✔️ 0 💤 0 ❌
287 runs  287 ✔️ 0 💤 0 ❌

Results for commit 66f2941.

♻️ This comment has been updated with latest results.

[pietervp]

Also update https://github.com/chili-publish/studio-sdk/blob/main/types/MediaConnector.d.ts to reflect the same changes, would be good to review if the complete api surfacce still matches what we expect.

[Dvergar]

Also update https://github.com/chili-publish/studio-sdk/blob/main/types/MediaConnector.d.ts to reflect the same changes, would be good to review if the complete api surfacce still matches what we expect.

Ooops, you mentioned it in chat and i completely overlooked that.

So I updated both media & font connectors, we do not have preview (font) in getcapabilities so this probably needs to be added as well but i'll prefer not to do it in this ticket.

Probably some more cleanup related to that will be done in scope of >> https://chilipublishintranet.atlassian.net/browse/EDT-1172

@evan-mcgeek May I have your eyes 👀 on the font connector side?

PS: I'll split again MediaCapabilities/FontCapabilities in a follow-up ticket.

[Dvergar]

Just adding some findings.

We do have

export enum MediaDownloadType {
    LowResolutionWeb = 'lowresWeb',
    HighResolutionWeb = 'highresWeb',
}

Was it an intended constraint to omit outputVideo & outputPdf?
Is it a standard for you WRS to start an enum entry with an uppercase?

[evan-mcgeek]

LGTM! The only thing left is to add a preview capability to the font connector

[brapoprod]

seems non-breaking to me

[pietervp]

Just adding some findings.

We do have

export enum MediaDownloadType {
    LowResolutionWeb = 'lowresWeb',
    HighResolutionWeb = 'highresWeb',
}

Was it an intended constraint to omit outputVideo & outputPdf? Is it a standard for you WRS to start an enum entry with an uppercase?

That was intentional, because WRS should only ever use one of those.