-
Hello, Piotr! I found a bug
**Describe the bug**
In `Params` processor when validation for a key with hash value fails then we get another error for a key with integer value (string containing i…
-
I'm trying to convert the [tinglesoftware/dependabot-azure-devops](https://github.com/tinglesoftware/dependabot-azure-devops/pull/1318#issuecomment-2348706955) community Dependabot implementation over…
-
## Feature request
Allow components to have unnamed keyword arguments when using `with_collection`
### Motivation
This would allow using generic initialize methods with unnamed parameters and…
-
As new user I would like to read some introduction which learn me key concepts behind generated directory tree. Some simple example like super-simple todolist application will be very helpful for newb…
-
## Describe the bug
The error message from dry-validation for incorrect key nesting in en.yml file for rule with nested params is giving wrong path.
## To Reproduce
Consider having such schema an…
-
This came from a discussion with Matt Wynne about when using an scenario outline, does each example group need to have a header row?
The answer is yes, but if you forget to do this, Gherkin doesn't c…
-
**Describe the bug**
I need a Contract that is valid for hashes where the `:data` key is either a `Hash` with defined structure or an `Array` of such `Hash`es:
```ruby
{ data: { type: 'records' }…
-
At the moment validation contract returns nice human-readable errors via translation backend. Being a robot, I do not like it and I'd prefer pure data object/hash to be returned.
Justification: I d…
-
## Describe the bug
When I have a field that’s required, but its value is a maybe (attribute :missing, Types::String.maybe` for example) not passing that field does not fail when I create an object…
-
## Describe the bug
I'm getting some fields included in errors that would normally be fine, in a very specific circumstance:
- Use some of the coercible types in a Struct
- Generate a schema fr…