Olivier Mélois
Olivier Mélois
Improving this will be binary breaking, so it's likely not gonna happen until the next minor version (0.18), which is gonna take a couple months at least. However, in a...
For collections, the content of the documentation is mostly correct, it's just that `@param` is the wrong annotation. We just need to drop it in favour of a custom header.
Yeah that's fine. As long as Maps have got `key` and `value`, and `list` have "member" or "content", it's all good
_sigh_ I'm really not liking the distinction between : * `@default s: Document` `s: Option[Document] = Some(Document.DNull)` * `@default s: Integer` `s: Option[Int] = None` I'm gonna have to digest...
> I'm just not a fan of the current semantics Agreed
This issue should be split in two that could be handled separately : 1. Generate empty structures as case objects (whether they're used in or out of unions) 2. Allow...
I'm having the exact same issue. As a matter of fact, I'm experimenting with your ops-mirror POC @bishabosha (https://github.com/bishabosha/ops-mirror), and that limitation of `derives` keyword prevents a world of interesting...
Mmm interesting, that may indeed work. Thanks :+1:
> The last discussion of this was that preserving refinements could lead to cyclic references but it's still worth revisiting to be sure If I may, I think it'd be...
This is likely the exact same bug as : https://github.com/eed3si9n/expecty/issues/54