Nicolas Maquet
Nicolas Maquet
Services implementing [Relay's Global Object Identification Spec](https://relay.dev/graphql/objectidentification.htm) (i.e. the `Node` interface) should be allowed to be configured as boundary types without the need for an additional boundary accessor field.
Supporting non-nullable boundary accessors adds a significant amount of complexity to the implementation of Bramble's query executor. This is due to [GraphQL's bubbling of errors to parents of non-nullable fields](https://spec.graphql.org/June2018/#sec-Errorsl)....
Bramble is currently a monolithic and opinionated gateway, which makes supporting all use cases quite difficult. Separating out Bramble's core gateway logic into its own importable package would allow more...
Shared enums would be really useful to define standard values across services. For example: ```graphql enum Gender @boundary { MALE FEMALE OTHER UNKNOWN } ``` Similarly, shared scalars would be...
In High Availability deployments, it would be desirable to allow Bramble to store the merged schema and the other bits of gateway state into an external consistent storage service (e.g....
Bramble relies on a custom directive called `@boundary` to determine which object types are shared across services and how to look up boundary objects by ID in queries. This was...
This would make federated queries more robust as one error in the resolution of the array wouldn't null-out the whole array. See https://github.com/movio/bramble/issues/51#issuecomment-954363331
The Meta plugin could be improved in the following ways: - Add `type(id: ID!): BrambleType` to `BrambleMetaQuery` - Add `service(id: ID!): BrambleService` to `BrambleMetaQuery` - Add `fields: [BrambleField!]!` to `BrambleService`...
Adds a new `autoSelect` boolean option (default is `true`) that controls whether the first search result should be automatically selected or not. Setting it to `false` is useful when using...