Everything resolves to strings

Hi there!

It seems to me that all typing resolves to string?

Example:

export type BorderStyleProperty = Globals | LineStyle | string;

Since it can be a string that will override both Globals and LineStyle, not giving intellisense on the possible properties of the border style.

Is this intentional?

I did some more research: https://github.com/Microsoft/TypeScript/issues/29729#issuecomment-471566609

[remorses]

Adding the string type to the union does not make much sense imo, you lose auto completion and type validation

[frenic]

@kylemh display can have combinations of values https://drafts.csswg.org/css-display/#the-display-properties so it would be wrong to remove | string from that property. I’ve given it some attempts to combine different values into multiple string literals and in that way be able to skip | string but it’s really complicated to do problematically and the type definitions exploded in size and performance issues became a concern so the progress halted.

I may give it another try soon thanks to this which will make things a bit easier. At least support a fragment of different combinations so display becomes complete without | string would be really nice. I’m well aware of the issue but you’re welcome to submit a separate issue if you’d like.