Setting default values does work for boolean props

🧐 Fixed the title! 😄

      default: false
      default_value: false
      examples: [false]

XB uses the first example value as the default. You should be able to see this at /admin/config/development/configuration/single/export: export the Component config entity for this SDC and you'll explicitly see the default_value in there.

Relevant docs: https://git.drupalcode.org/project/experience_builder/-/blob/0.x/docs/co... — but that does NOT state that that is used as the default value. A slight tweak to that simple bullet would go a long way I think :)

This means the test coverage in ui/tests/e2e/prop-types.cy.js is incomplete:

  it('Boolean', () => {
    cy.waitForElementContentInIframe('#test-bool code', 'true');
    cy.waitForElementContentNotInIframe('#test-bool code', 'false');
    cy.findByLabelText('Bool')
      .assertToggleState(true)
      .toggleToggle()
      .assertToggleState(false);

    cy.waitForElementContentInIframe('#test-bool code', 'false');
    cy.waitForElementContentNotInIframe('#test-bool code', 'true');
  });

— Any chance you could add the missing test coverage? 🙏

Actually, I think this is clearer still.

— Any chance you could add the missing test coverage? 🙏

All signs point to probably not 😭. NW and slowly backs away.

Also, SDC allows default: … because it's part of JSON Schema itself, but the SDC subsystem doesn't actually use/support it. I observed this 4 months ago at #3462705-19: [META] Missing features in SDC needed for XB → .

IOW: you're running into one of many SDC bugs/oversights we've spotted while working on XB, see 📌 [SPIKE] Comprehensive plan for integrating with SDC Active for the overview :)

I thought I already reported this a long time ago… hmm… maybe it was closed

🐛 [PP-1] Can't toggle boolean prop back to true after changing to false Postponed was marked as duplicate but never got fixed it seems

Thanks for bumping priority :) I find that I’ll set to false and the component behavior seems fine but the UI later shows it as true even though the component still seems to behave as it’s false … maybe that’s what’s explained but I’m on my phone on my flight to Atlanta so hard to read well :D