dgs-framework
dgs-framework copied to clipboard
Netflix
GraphQL for Java with Spring Boot made easy.
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3 to 4. Release notes Sourced from actions/upload-artifact's releases. v4.0.0 What's Changed The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts....
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Pull Request type ---- - [ t] Bugfix - [X] Feature - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ]...
bug: @DgsEntityFetcher annotation does not prevent compilation when method arguments are incorrect
## Expected behavior WHEN an entity fetcher is defined as such: ```java @DgsEntityFetcher(name = DgsConstants.STORE.TYPE_NAME) public Store storeFetcher(final DgsDataFetchingEnvironment dfe, final Map values) { return Store.newBuilder().name("myStore").build(); } ``` THEN compilation...
### Add a new `Advanced` documentation entry that explains how to configure and use the the `graphql-dgs-extended-validation` module to add your own custom validation rules. While I was adding `graphql-dgs-extended-validation`...
Please read our [contributor guide](https://github.com/Netflix/dgs-framework/blob/master/CONTRIBUTING.md) before creating an issue. In my opinion, the issue is not a common situation. - I wrote the code as below  ## Expected behavior...
I found problems with both `graphql-transport-ws` and `graphql-ws` in webflux (reactive) mode. Using `graphql-transport-ws` it is not possible to subscribe more than once with different ids, while `graphql-ws` does not...
Please read our [contributor guide](https://github.com/Netflix/dgs-framework/blob/master/CONTRIBUTING.md) before creating an issue. ## Expected behavior Application should start without this Issue ## Actual behavior  ## Steps to reproduce Create normal Spring Project...
According to the [spec](https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md#examples), it doesn't really define what should happen if the client receives a message before the connection ack message. Some GQL servers such as Hasura (see https://github.com/hasura/graphql-engine/issues/7002)...
when making a subscription, the websocket simply to emit data and close after some time, I am using the latest version.
