You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dataModelBindings component prop now supports both object and string types. However, there is an unintended shortcut in the code that prevents typescript from raising errors in some cases, such as in the convertDataBindingToInternalFormat function.
To address this, we need to update the type definition and handle the resulting typescript errors when the InternalBindingFormat type is properly introduced.
The convertDataBindingToInternalFormat works for some reason, even tho the const dataModelBinding is always a string according to typescript.
Additional Information
No response
Tasks
In global.ts, update the type definition line 19 to: export type IDataModelBindings = KeyValuePairs<string | InternalBindingFormat>;
Resolve the typescript errors that will arise throughout the codebase after adding InternalBindingFormat to the type definition.
Acceptance Criterias
No response
The text was updated successfully, but these errors were encountered:
Description
The
dataModelBindings
component prop now supports both object and string types. However, there is an unintended shortcut in the code that prevents typescript from raising errors in some cases, such as in theconvertDataBindingToInternalFormat
function.To address this, we need to update the type definition and handle the resulting typescript errors when the
InternalBindingFormat
type is properly introduced.The
convertDataBindingToInternalFormat
works for some reason, even tho the constdataModelBinding
is always a string according to typescript.Additional Information
No response
Tasks
global.ts
, update the type definition line 19 to:export type IDataModelBindings = KeyValuePairs<string | InternalBindingFormat>;
Acceptance Criterias
No response
The text was updated successfully, but these errors were encountered: