Why context is missing in the MessageDescriptor type, but works?

[MurzNN]

I need to add a context to some messages in my project, for this, the context property can be used according to the documentation, and it works! Here is an example:

const text1 = i18n.t(/* i18n */ { id: 'right_direction', message: 'Right', context: 'direction' })
const text2 = i18n.t(/* i18n */ { id: 'right_check_result', message: 'Right', context: 'check result' })

But, it produces a typescript error:

Object literal may only specify known properties, and 'context' does not exist in type 'MessageDescriptor'.

because the context property is missing in the type declaration:

type MessageDescriptor = {
    id: string;
    comment?: string;
    message?: string;
    values?: Record<string, unknown>;
};

So, the question is - why the context property is missing in the type declaration? If this is correct, then why does it work?

If not correct, what is the correct approach to pass the context?

[timofei-iatsenko]

I think you already figured out that it doesn't work in the way as it intended

#2490 (comment)

The context is only consumed and makes sense when macro applied. Hence only MacroMessageDescriptor type defines it.

If by "it works" you mean, extractor pick it up to the catalog - then yes, extractor does not analyze the scopw, when it sees an object with properties it will extract all properties it knows how to handle.

[MurzNN]

Thank you for the explanation! By "it works" I meant the extractor, but if we already set the custom ids, there is no need to pass the context.