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
By changing the type definition (in a patch release!!!) for formatter, our build broke. Our formatter uses (value: string) => JSX.Element and is now an invalid formatter because of the limiting of the formatter to return a ValueType and a NameType or just a ValueType.
Moreover, the goal of a formatter is to provide a different representation for ValueType. In my case I have <Tooltip<number,string> ... /> where the number is an amount (currency). The displayed value of the number is a string and not a number type (e.g. "$1,000.00").
I think this was fixed via #3618 and is part of the v2.7.0 release.
The original return type ([React.ReactNode, React.ReactNode]) for the custom tooltip formatter is back, which works for me.
By changing the type definition (in a patch release!!!) for
formatter
, our build broke. Our formatter uses(value: string) => JSX.Element
and is now an invalid formatter because of the limiting of the formatter to return aValueType
and aNameType
or just aValueType
.It's wrong to do this in a patch version.
Broken in #2924
The text was updated successfully, but these errors were encountered: