wundergraph
wundergraph copied to clipboard
> Potential request smuggling capabilities due to lack of input validation | Details | | | ------------------- | ---------------------------------------------- | | Package | `actix-http` | | Version | `0.2.11` |...
> Multiple Transfer-Encoding headers misinterprets request payload | Details | | | ------------------- | ---------------------------------------------- | | Package | `hyper` | | Version | `0.12.35` | | URL | [https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf](https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf)...
> difference is unmaintained | Details | | | ------------------- | ---------------------------------------------- | | Status | unmaintained | | Package | `difference` | | Version | `2.0.0` | | URL...
> Use-after-free in BodyStream due to lack of pinning | Details | | | ------------------- | ---------------------------------------------- | | Package | `actix-http` | | Version | `0.2.11` | | URL...
> Use-after-free in Framed due to lack of pinning | Details | | | ------------------- | ---------------------------------------------- | | Package | `actix-codec` | | Version | `0.1.2` | | URL...
> failure is officially deprecated/unmaintained | Details | | | ------------------- | ---------------------------------------------- | | Status | unmaintained | | Package | `failure` | | Version | `0.1.8` | |...
In a query like the following: ```gql query { Hero { __typename } } ``` The expected response would contain a key like: ```gql "__typename": "Hero" ``` Instead, the `__typename`...
As mentioned in [#3](./3#issuecomment-646595412) [CI bench checks](https://github.com/weiznich/wundergraph/blob/master/.github/workflows/ci.yml#L118-L122) run faultless despite the struct https://github.com/weiznich/wundergraph/blob/ffbb883eea169d1750659e038d7051a84b21f6e7/wundergraph_bench/src/api.rs#L553-L557 doesn't contain two fields, which are set as primary key for the table https://github.com/weiznich/wundergraph/blob/ffbb883eea169d1750659e038d7051a84b21f6e7/wundergraph_bench/src/api.rs#L287-L293
This one should be quite easy: - [ ] Add corresponding feature flags to the `wundergraph_derive`, `wundergraph` and `wundergraph_cli` crate - [ ] Generate an impl for `LoadingHandler` for `diesel::mysql::Mysql`...
This PR doesn't solve the issue #3 entirely. It doesn't contain implementation of insert mutation for Mysql. Consequently `wundergraph_example` doesn't support Mysql also