wabrit
wabrit
Using: - rover version 0.6.0 or 0.7.0 - apollo federation v2 According to the [docs](https://www.apollographql.com/docs/federation/federated-types/composition#enums), composition of enums uses either the union or intersection strategy depending on whether the enum...
The current Apollo v2 federation docs state: > Custom directives are not included in your graph’s composed supergraph schema. The composition process strips all subgraph directives. Only a given subgraph...
### Summary If a subgraph schema uses a custom directive that alters the schema element to which it is applied, this is not detected using the `_service { sdl }`...
### Software versions _Please provide at least OS and version of pact-js_ - **OS**: Windows 10 Enterprise - **Consumer Pact library**: @pact-foundation/pact 10.0.0-beta.58 - **Provider Pact library**: n/a - **Node...
### Software versions - **OS**: Windows 10 - **Consumer Pact library**: Pact JS 10.0.0-beta.58 - **Node Version**: v16.13.2 ### Expected behaviour Using arrayContaining matcher should work regardless of nesting level...
Using GraphQL plugin 4.0.2 on WebStorm 2023.2.5 Valid `directive` declarations in schema files are flagged by default as "Unknown directive location" even though the locations in question are valid. 
Using GraphQL plugin 4.0.2 on WebStorm 2023.2.5 The GraphQL meta-field `__typename` appears not to be recognised when included in GraphQL documents; an error of the form e.g. `Unknown field "__typename"...
Adds the ability to assert that Events have been raised on Observations; matching can be done against event name only, or event name and contextual name. Resolves #5576
**Please describe the feature request.** The `micrometer-observation-test` dependency does not appear to offer a simple way of asserting on observation events in tests **Rationale** The `TestObservationRegistryAssert` class handles assertions on...