length rule and cross rules, n arg fix, coerce arg change

Author: LJ-Jenkins

.gitignore

@@ -6,3 +6,5 @@
 .quarto
 docs
 inst/doc
+/doc/
+/Meta/

NEWS.md

@@ -1,5 +1,19 @@
 # fluffy (development version)
 
+## New Features
+
+* New `length` rule added to the `Registry`. This rule checks that the length of a data field is exactly equal to the value specified by the `length` schema field. This removes the need to specify both a `min_length` and `max_length` with the same value when enforcing an exact length. 
+
+* New `length_and_min_length` and `length_and_max_length` cross rules added to the `Registry`. These rules check that the `min_length` and `max_length` rules are not specified when a `length` rule is present.
+
+* The `coerce` rule now accepts functions with multiple arguments when passed directly to a `Schema` or `Validator`, allowing base `as.*()` functions to be used as `coerce` rules in schema definitions. However, only the field value is passed to the function; any additional arguments are ignored. Functions with multiple arguments still cannot be added to the `Registry@coerce_map`, as `add_coerce_rule()` enforces a strict one-argument function signature.
+
+## Bug fixes
+
+* Fixed the `allowed_type_mismatch` and `forbidden_type_mismatch` cross rules so that they use the `Registry@type_map` to obtain the function used for type checking when `type` is a string, and use the supplied function directly when `type` is a function. Previously, function-valued `type` fields caused an error, while character-valued `type` fields could result in incorrect type checking because the class of the `allowed`/`forbidden` field was compared directly with the `type` field. This could produce false positives, such as an integer `allowed`/`forbidden` field being flagged as a type mismatch when `type` was "numeric".
+
+* Fixed incorrect argument-count checking for the `type`, `predicate`, and `apply` rules.
+
 # fluffy 1.0.0
 
 * Initial CRAN submission.

R/aaa_Schema.r

@@ -74,6 +74,13 @@
 #' [adding custom rules](../doc/custom-rules.html).
 #' @seealso [add_rule] for adding rules to a `Registry`. [Validator] for
 #' validating data against a `Schema`.
+#' @note
+#' The `coerce` rule may use functions with multiple arguments when
+#' passed directly to a `Schema` or `Validator`. Only the field value is
+#' passed to the function, and any additional arguments are ignored. Thus,
+#' `as.numeric` is valid as a `coerce` rule in a schema definition, but cannot
+#' be added to a `Registry`, which enforces a strict one-argument function
+#' signature.
 #' @examples
 #' # A valid schema
 #' s <- Schema(list(

R/abb_add_rule_generics.r

@@ -71,6 +71,11 @@
 #' (the full schema/data in the respective walks) are named arguments
 #' and must be named as such.
 #'
+#' The `coerce` rule may use functions with multiple arguments when
+#' passed directly to a `Schema` or `Validator` (additional arguments are
+#' ignored), but `Registry` addition is stricter and enforces a single
+#' argument function signature.
+#'
 #' Despite [Registry] using environments to store rules, which are
 #' mutable, [add_rule] methods copy the existing environment
 #' and the new rule into a new environment, meaning that the