Fix typehint on enums to reflect that AWS might add new values

[jderusse]

No description provided.

[GrahamCampbell]

Hmmm, but the type RuntimeName::*|string is identical to string, so we lose the value of having the specific string values.

[jderusse]

Hmmm, but the type RuntimeName::*|string is identical to string, so we lose the value of having the specific string values.

Yeah, that's true. See the reasoning here #1921 (comment)

[stof]

Based on the analysis of the official JS SDK (see #1921 (comment)), I'm not sure we should do this change.
Our current approach (returning the string as is but documenting the type as being one of the known values) is exactly what AWS does in their own SDK for JS and Typescript users.

[jderusse]

Based on the analysis of the official JS SDK (see #1921 (comment)), I'm not sure we should do this change. Our current approach (returning the string as is but documenting the type as being one of the known values) is exactly what AWS does in their own SDK for JS and Typescript users.

I agree.

I took time to think about that and finally agreed with your initial suggestions. Returning a special a sdk unknown value.

I don't like adding an overhead for edge cases... but that the single way to make the typehint useful.

Or we just let it like that (like is does) and continue adding exception to PHP Stan.