Update manifest combinations

[kancijan]

Description

Fix for manifest combinations when the value is a boolean in string. E.g., "true" or "false."
Previously, this would fail due to checkAttr() returning a boolean false that would fail on the first !value check.

[iruzevic]

Why would you have boolean in string?

[kancijan]

Why would you have boolean in string?
@iruzevic

[iruzevic]

I don't understand. Why this can't be bool like it is defined in the attributes?

[kancijan]

@iruzevic because we have toggles and when checking false we have false positive in first check. This logic is already implemented in PHP.

eightshift-frontend-libs-tailwind/scripts/editor/tailwindcss.js

Line 193 in 893fb69

if (!value) {

I'm now testing another approach suggested by Goc.

[kancijan]

A new conclusion is that we have a misleading schema setup.

Booleans were supported, but the warning messages made me believe that strings must be used.

I'll revert the logic in the libs and update the schema. Also, update manifests in existing blocks and components that use combinations.