From 697544a55a105bce2818f31734dc351077757abc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Erik=20L=C3=B6vmo?= <erik.lovmo@icloud.com>
Date: Thu, 4 Dec 2025 14:03:06 +0100
Subject: [PATCH] Remove incorrect note about combining `values` and
 `allow_blank`

The example is incorrect: you can, in fact, not supply a blank
value to `state` with that `params` block.
---
 README.md | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/README.md b/README.md
index 5e6112896..4f7cd52c1 100644
--- a/README.md
+++ b/README.md
@@ -1702,14 +1702,6 @@ end
 
 While Procs are convenient for single cases, consider using [Custom Validators](#custom-validators) in cases where a validation is used more than once.
 
-Note that [allow_blank](#allow_blank) validator applies while using `:values`. In the following example the absence of `:allow_blank` does not prevent `:state` from receiving blank values because `:allow_blank` defaults to `true`.
-
-```ruby
-params do
-  requires :state, type: Symbol, values: [:active, :inactive]
-end
-```
-
 #### `except_values`
 
 Parameters can be restricted from having a specific set of values with the `:except_values` option.