why need | string in the properties like display

[xwchris]

In the source code, I found the property display's type like this

type DisplayProperty = Globals | DisplayOutside | DisplayInside | DisplayInternal | DisplayLegacy | "contents" | "list-item" | "none" | string;

the result of DisplayProperty is string because of the | string. As a result of this, I can't have a autocompletion in ts.

So why need | string in the properties like display?

[frenic]

As mentioned here #8 (comment) the syntax for display tells us that you're able to use space separated values. That's why union string is needed. But the autocomplete however seems to be solved in #74. So it will hopefully work in v3 that will be released soon.