Why is the second parameter of getUiOptions() sometimes omitted?

[caillou]

In order to understand how to write my own templates and widgets, I studied the core components. In doing so, I observed the following:

getUiOptions takes two parameters, uiSchema and the globalOptions from the registry.

getUiOptions(uiSchema?: UiSchema<T, S, F>, globalOptions?: GlobalUISchemaOptions)

In packages/core/src/components is see it often used without the second parameter.

Is this omission accidental, or am I missing a bigger picture?

[nickgros]

Today, our globalOptions only apply to a subset of features, so only the components that care about possible globalOptions access it and pass it into getUiOptions. As the features supported in globalOptions change, we may end up using the second parameter more often.