protovalidate 0.1.0.beta3-x86_64-linux-gnu → 0.1.0-x86_64-linux-gnu
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 98a4d19267fe4ade7c74dc08ce0ec1cca54b2b72d63ed743a7e9c79f7f1d98c8
|
|
4
|
+
data.tar.gz: 6cc4a94d98b34efa8d4bf04d3f0bda5ab27f8cd4fd135f222f91c658cc1c7c92
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: fc1a6017a7c4cc296fe6a90bbb683b74b6dd323fe024ef28764265c851424ea5d46ef360cb90dad5a18f0bca4dac1436d9ed74e5e472cd621c065a7cf3f6b0ed
|
|
7
|
+
data.tar.gz: 2aef96a8b03705211add946f25c48341757f7e44be2e4ddf9b061cd9800a8dd5119870f08f546a0eccc52052043dd5f10b5df9513a6eb4712d0394780a393813
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.0 (2026-10-14)
|
|
4
|
+
|
|
5
|
+
- Graduate beta.
|
|
6
|
+
|
|
3
7
|
## 0.1.0.beta3 (2026-09-22)
|
|
4
8
|
|
|
5
9
|
- `Protovalidate.register` and `Validator#register` compile the rules of message types ahead of their first validation, so the compilation, which blocks concurrent validations, can run at boot instead of inside a request. `register_all` does the same for every loaded message class.
|
data/README.md
CHANGED
|
@@ -83,12 +83,12 @@ The rules of a message type are compiled the first time a message of that type i
|
|
|
83
83
|
Protovalidate.register(Example::User, Example::Order)
|
|
84
84
|
```
|
|
85
85
|
|
|
86
|
-
`Protovalidate.register_all` registers every message class loaded so far instead of a hand-maintained list, so call it once all generated code has been loaded. In a Rails application, `config.after_initialize` callbacks run in the `finisher_hook` initializer, after the `eager_load!` initializer, so with `config.eager_load` enabled every generated class under an autoload path is already loaded by then. Generated code outside the autoload paths, such as under `lib/`, must be required before the callback runs.
|
|
86
|
+
`Protovalidate.register_all` registers every message class loaded so far instead of a hand-maintained list, so call it once all generated code has been loaded. In a Rails application, `config.after_initialize` callbacks run in the `finisher_hook` initializer, after the `eager_load!` initializer, so with `config.eager_load` enabled every generated class under an autoload path is already loaded by then. Without eager loading, only the classes loaded so far are registered and the rest compile on first use. Generated code outside the autoload paths, such as under `lib/`, must be required before the callback runs.
|
|
87
87
|
|
|
88
88
|
```ruby
|
|
89
89
|
# config/initializers/protovalidate.rb
|
|
90
90
|
Rails.application.config.after_initialize do
|
|
91
|
-
Protovalidate.register_all
|
|
91
|
+
Protovalidate.register_all
|
|
92
92
|
end
|
|
93
93
|
```
|
|
94
94
|
|
|
Binary file
|
|
Binary file
|
|
Binary file
|