✅ Deploy Preview for unocss ready!

Name	Link
🔨 Latest commit	9c5976f
🔍 Latest deploy log	https://app.netlify.com/sites/unocss/deploys/666868ab9484db0008266092
😎 Deploy Preview	https://deploy-preview-3810--unocss.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Wouldn't this break anything that depended on h.properties?
For an example, transition-height and etc would completely break.

This is why the `targets' test is failing.

Since this PR adds a composite prop to the CSS props array in handler utils, it more or less breaks the whole prop resolving mechanism.

I think the better approach is to remove the composite prop from that handler array, and guard the h.properties value like the codebase has done before. Moreover, since h.properties only returns valid CSS values, we don't have to transform it further.

So an approach like this passes the test cases. Though for some odd reason the snapshot matching fails.

1. Early return when properties are valid CSS properties.
2. Transform the "custom" properties, filter undefined ones, and only return a valid string when the array itself is populated.

function transitionProperty(prop: string): string | undefined {
  const cssProps = h.properties(prop)
  if (cssProps !== undefined)
    return cssProps

  const transformed = prop.split(',').flatMap(x => transitionPropertyGroup[x]).filter(x => x !== undefined)
  return transformed.length > 0 ? transformed.join(',') : undefined
}