@hammerstone/refine-stimulus
Advanced tools
Comparing version 2.6.0 to 2.6.1
@@ -0,1 +1,4 @@ | ||
### 2.6.1 | ||
* Add configuration option `date_lte_uses_eod` to include a whole day in the range when using a <= comparison | ||
* Fix a bug where option condition selections were being forced to the first value | ||
### 2.6.0 | ||
@@ -2,0 +5,0 @@ * Prevent users from adding criteria if values for existing criteria are blank |
{ | ||
"name": "@hammerstone/refine-stimulus", | ||
"version": "2.6.0", | ||
"version": "2.6.1", | ||
"description": "Refine is a flexible query builder for your apps. It lets your users filter down to exactly what they're looking for. Completely configured on the backend.", | ||
@@ -5,0 +5,0 @@ "browserslist": [ |
@@ -240,2 +240,10 @@ ## How to integrate the refine filter | ||
## Tweaking Date Comparison behavior | ||
You may run into a situation where users can only pick whole days that are being compared to a date column. In this case, the default less than or equal behavior will compare to the current time on the day selected, which may exclude some records the user intended to include. To include the entire selected day in the range, you can set the following in an initializer: | ||
# config/initializers/refine_rails.rb | ||
```ruby | ||
Refine::Rails.date_lte_uses_eod = true | ||
``` | ||
## Local JavaScript Development | ||
@@ -242,0 +250,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
293158
340