Niccolò Belli
Niccolò Belli
`createSchemaForApollo` won't be supported anymore in 3.0 and `fieldResolver` can be emulated applying a custom directive in `schemaBuilder`, so I think this can be closed.
I'm not using docker though I get the same issue on Arch Linux.
Damn that's it then, zfs 2.2 on a PCIe4 NVME here.
> Maintaining version consistency across a monorepo is a painful chore. This is indeed the main reason why I migrated [accounts.js](https://github.com/accounts-js/accounts) to yarn v4. The integrated `upgrade-interactive` plugin makes it...
I have the same issue with typescript-axios: all properties are optional.
I guess the root of the problem is badly made swagger definitions, I'm trying to get these fixed.
@VincentVanclef AFAIK you need to fix your swagger definitions, I didn't find any other way to force the properties to be non-optional
Please note that the build is currently broken in the next branch, see https://github.com/react-native-elements/react-native-elements/pull/3858
I've tried the PR but it didn't work. The easiest workaround is the following: ```ts const theme = createTheme({}); ``` `const theme = {}` despite being allowed by the typings...
I've tried your PR but unfortunately it doesn't fix the issue for me.