-
**[Mingle Card: 1694](https://liquidframeworks.mingle.thoughtworks.com/projects/alpine_mobile/cards/1694)**
Add validation rule to enforce StartTime
-
**[Mingle Card: 1708](https://liquidframeworks.mingle.thoughtworks.com/projects/alpine_mobile/cards/1708)**
Update ticketmetadata sync step to pull validation rules (a static resource)
-
**[Mingle Card: 1709](https://liquidframeworks.mingle.thoughtworks.com/projects/alpine_mobile/cards/1709)**
Update jobmetadata sync step to pull validation rules (a static resource)
-
Current rules:
```
In addition to the gossip validations for the `beacon_block` topic from prior specifications, the following validations MUST pass before forwarding the `signed_beacon_block_and_bl…
tbenr updated
10 months ago
-
I can't give custom messages.
public function rules() {
$rules = [
'card_number' => ['required', new CardNumber],
'expiry_year' => ['required', new CardExpiratio…
-
It would be really cool if the generated TypeScript types were aware of `protovalidate` rules.
For example
- dropping the `?` optional qualifier for message fields with `required`
- dropping th…
-
So that this can be used by things like choco
-
**Describe the bug**
We are trying to automatically assign data products to datasets and their container during ingestion from S3. I have included the format of our transformer below:
**To Reprodu…
-
Currently, our `RecordValidators` only run on uncommitted records; however, we have come across a few client-apps that expect validation to run on records created via calls to `loadData` and `updateDa…
-
Context #3282 by @spawnia
It looks like we have the following mismatch between spec and graphql-js.
For example, type names are checked using this rule:
https://github.com/graphql/graphql-js/blo…