No labels are displayed for boolean fields

I would suggest the facet label or the field label as label for the checkbox.
have the same issue - tried "Translate entity label" to tick, but it breaks the site.

A workaround is to jQuery a label in there:
$('[data-drupal-facet-item-id="facet_id"] span').text('Your label here');
where facet_id is easily found by looking at the HTML output.

Additionally, you can set it to be a single checkbox if it is a boolean value by checking `exclude specified items` and excluding item `0` in the facet settings.

I would solve this one but I would first like to hear other opinions on the solution:
Add to the facet form another processor (similar with Count limit) - a checkbox "Boolean label" that will expand two input fields for On / Off values.

Showing labels from the field settings I'm not seeing it reliable because On/Off labels are per field instance and each instance could use different labels. Also boolean are Published, Sticky attributes, which don't have on/off labels.

Another processor plugin is a good solution. I'm pretty sure we need to find a way to use the boolean's actual on/off values. But we can do that in a follow-up.

For now the way to resolve this is:

- Create a new processor (Display label for boolean fields)
- Transform into 0/1 On/Off.
- Open a followup to read the actual values from the config.

Discussed this with @swentel, we can read this from BooleanItem's field settings.

Added a patch with a processor to set On/Off values.
I will add a test soon.

This is looking great! Very cool.

1. +++ b/src/Plugin/facets/processor/BooleanItemProcessor.php
   @@ -0,0 +1,155 @@
   + * Provides a count limit processor.
   

   Needs an update.

2. +++ b/src/Plugin/facets/processor/BooleanItemProcessor.php
   @@ -0,0 +1,155 @@
   +   * Constructs a Drupal\Component\Plugin\PluginBase object.
   

   Needs an update.

3. +++ b/src/Plugin/facets/processor/BooleanItemProcessor.php
   @@ -0,0 +1,155 @@
   +      '#states' => [
   +        'required' => ['input[name="facet_settings[boolean_item][status]"' => ['checked' => TRUE]],
   +      ],
   ...
   +      '#states' => [
   +        'required' => ['input[name="facet_settings[boolean_item][status]"' => ['checked' => TRUE]],
   +      ],
   

   Nice!

4. +++ b/src/Plugin/facets/processor/BooleanItemProcessor.php
   @@ -0,0 +1,155 @@
   +  public function defaultConfiguration() {
   +    return array(
   +      'on_value' => 1,
   +      'off_value' => 0,
   +    );
   

   Let's use "On"/"Off" as default values here to have a sane default by just enabling the processor.

I've updated the patch.

I've added a test, but it requires boolean field on the test data. Because the testing content structure comes from search_api, I'm not sure if I should open a ticket there or change this particular test to use a structure defined in facets module.

Not sure how we should do that either. I'll discuss that with @drunken monkey to find a solution.

Huge thanks for the work you did on this!

We can add our own fields on top of the already existing fields. This is already happening in HierarchicalFacetIntegrationTest

The patch in #11 doesn't apply anymore. It needs to be rerolled and merged with the patch in #10.

That's a good start to finish the test.

This combines #11 and #10.

Resting - that looks like a random fail,

Committed, thanks!

@borisson ,

How to fix the issue in drupal 7

TKS