Fixed Hint message type

[adids1221]

Description

After changing Hint message prop type in this PR which became a bit lossy type, changing the message type to be ContentType more strict type.

Changelog

Hint message prop type fix.

Additional info

None

[adids1221]

@Inbal-Tish we can discuss about the comment in the old PR when the user passing null as Andrew mentioned there.

[Inbal-Tish]

@Inbal-Tish we can discuss about the comment in the old PR when the user passing null as Andrew mentioned there.

Ok. Why do we want to support null? The massage prop is rendered in a Text component, why should we let the user pass null or number or boolean for that matter?

[adids1221]

I think the only case using null is when the user has some state with the message and sometime the state is set to null

I can think of 2 use cases:

1. there is a state that the user set to null sometime which isn't right.
2. the user is passing Text element which is and ReactElement with null value inside - Andrew case.

[Inbal-Tish]

I think the only case using null is when the user has some state with the message and sometime the state is set to null

I can think of 2 use cases:

1. there is a state that the user set to null sometime which isn't right.
2. the user is passing Text element which is and ReactElement with null value inside - Andrew case.

Not our business to fix. If the user doesn't want to render a message don't pass the prop, if using react element it's the user's responsibility to pass it correctly (check the value before passing the element, for example:
massage={sometext && <Text>someText</Text>}