Kiryl Mialeshka
Kiryl Mialeshka
**Summary:** _Briefly describe the changes made in this PR._ **Issue Reference(s):** Fixes #... _(Replace "..." with the issue number)_ **Build & Testing:** - [ ] I ran `cargo test` successfully....
**Summary:** _Briefly describe the changes made in this PR._ **Issue Reference(s):** Fixes #... _(Replace "..." with the issue number)_ **Build & Testing:** - [ ] I ran `cargo test` successfully....
Consider the next types: ```rust #[derive(JsonSchema)] enum Enum { Var1(String), Var2(u32) } #[derive(JsonSchema)] struct FlattenOptionEnum { #[serde(flatten)] enum_: Option } ``` The generated schema looks like ```json { "$schema": "https://json-schema.org/draft/2020-12/schema",...
**Summary:** _Briefly describe the changes made in this PR._ **Issue Reference(s):** Fixes #... _(Replace "..." with the issue number)_ **Build & Testing:** - [ ] I ran `cargo test` successfully....
**Summary:** _Briefly describe the changes made in this PR._ **Issue Reference(s):** Fixes #2817 **Build & Testing:** - [ ] I ran `cargo test` successfully. - [ ] I have run...
In some cases batched request could be resolved to multiple values for every entry of the batched parent value. The logic is already implemented for the `@http` dataloader depending on...
Resolvers on types could use different fields from the respective type inside the resolver itself. Add a validation that every field that is used as `.value.field_name` inside the resolver is...
Current implementation is checking only the fields while calculating n+1 issue. But after implementing https://github.com/tailcallhq/tailcall/issues/2639 resolvers could now be defined on types as well. When considering entity resolver the entity...
For `dynamic-schema` allow to add type directives to the schema.