Range field

[blondie63]

I'm trying to use this field but docs https://backpackforlaravel.com/docs/6.x/crud-columns#range-1 not working for me..
Is it a bug or i'm wrong ? this is my code:
CRUD::addField([
'name' => 'send_notification_reminder_days_back',
'label' => trans('backpack::ash_base.site_fields.send_notify_reminder_days_back'),
'type' => 'range',
'min' => 0,
'max' => 1,
'showValue' => true,
'tab' => trans($this->tabNotifications)
]);

[backpack-ai-bot[bot]]

Based on the knowledge sources, your usage of the range field is mostly correct, but there are a few details to clarify:

1. Field Options: The Backpack documentation for the range field shows that you should use the attributes array to set min and max values, not as top-level keys. Your code uses 'min' and 'max' as top-level keys, which may not be recognized by Backpack. Instead, you should use the 'attributes' key:

CRUD::addField([
    'name' => 'send_notification_reminder_days_back',
    'label' => trans('backpack::ash_base.site_fields.send_notify_reminder_days_back'),
    'type' => 'range',
    'attributes' => [
        'min' => 0,
        'max' => 1,
    ],
    'showValue' => true,
    'tab' => trans($this->tabNotifications)
]);

This matches the example from the official documentation:

CRUD::field([   // Range
    'name'  => 'range',
    'label' => 'Range',
    'type'  => 'range',
    //optional
    'attributes' => [
        'min' => 0,
        'max' => 10,
    ],
]);

Backpack Docs: Range Field

2. showValue Option: The documentation does not mention a showValue option for the field type. This option is available for the range column type (for displaying in the table), not for the field input. If you want to show the value next to the slider, you may need to customize the field or check if a newer version of Backpack supports this feature for fields. As per the docs, this is not a standard field option.

3. Bug or Misconfiguration: If the field is not rendering as expected, it is likely due to the use of 'min' and 'max' as top-level keys instead of inside 'attributes'. Try updating your code as shown above.

If you still experience issues after this change, please provide more details about the error or how it is not working, as the knowledge sources do not mention a current bug with the range field itself.

Summary:

• Move 'min' and 'max' inside an 'attributes' array.
• The showValue option is not documented for fields.
• If issues persist, it may be a misconfiguration rather than a bug.

Let me know if you need further help!

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): [BUG] Date_range start_name value always falls back to default
[Feature] Range Filter (FROM/TO) allow single
CRUD Fluent API|Examples Part 2
Fields|date_range PRO
Github Issue (closed): [Bug] field date_range select ranges invalid date
Github Issue (closed): [4.1][Bug] String field wrapper attribute values interpreted as functions
Filters PRO|Range
Github Issue (closed): [Bug] date_range field inside repeatable field doesn't work
Fix the date range field
Github Issue (closed): [Bug] V6 date_range with FakeFields
Columns|range
Github Issue (closed): Range filter not applied if just one value entered
Github Issue (closed): docs about range field type

[blondie63]

For my test this range field is not working as aspected..