Koen Punt
Koen Punt
When testing the response of a nested query it would be practical to perform assertions on a subpath. To give an example; ```kt graphqlClient.document(query).execute() .path("addCartItemOptions.cart.id").isEqualTo(cartGlobalId) .path("addCartItemOptions.cartItem.id").isEqualTo(cartItemGlobalId) .path("addCartItemOptions.cartItem.options[0].productOption.name").isEqualTo(optionProduct1.name) .path("addCartItemOptions.cartItem.options[0].quantity").isEqualTo(1) .path("addCartItemOptions.cartItem.options[1].productOption.name").isEqualTo(optionProduct2.name) .path("addCartItemOptions.cartItem.options[1].quantity").isEqualTo(2)...
This allows for unparsed forwarding of graphql arguments, in the case something application specific has to be done with the arguments. The library already supports passing all of the input...
In graphql there's a difference between a null passed as input, and not providing the input value at all. Inspired by the type that graphql-kotlin provided, I've introduced an `OptionalInput`...
I want to have 2 dataloaders; 1 for loading `Location` entities by id, the other for loading entities by sublocation id. Both ids are UUIDs. The registry doesn't support registering...
I'm having trouble combining DataLoaders with Spring Security; My scenario; ```kotlin typealias MerchantDataLoader = DataLoader // MerchantDataLoader registry.forTypePair(UUID::class.java, Merchant::class.java).registerMappedBatchLoader { merchantIds, _ -> Mono.just(merchantService.getMerchants(merchantIds).associateBy { it.id }) } // ......
Is it possible to remove/unset a property of a `Yams.Node` object? I'm able to add or replace properties quite easily; ```swift var data = try Yams.compose(yaml: yamlString) data["SomeAdditionalProp"] = Yams.Node(displayName)...
Hi, I have an issue using the tool; it errors out with a segmentation fault. This both happens with the precompiled version and when I compile it myself. Click to...
This change makes using bundler optional More on this here: https://github.com/capistrano/bundler#usage
When running a play with `--check` flag, the task fails with the following message: ``` TASK [monit : monitors - Remove unused monitors] ******************************* fatal: [123.345.567.789]: FAILED! => {"failed": true,...
Not sure if this typo is made somewhere else in the source