Rémi Alvergnat

Here it is : https://gist.github.com/Toilal/9e9d4eaaeb3ec7650e742e0484510977 So it works like @qubitron first example, but handles primary keys and relationships properly by introspecting the SQLAlchemy model. At the moment, relationships are simply...

Pull request opened: https://github.com/graphql-python/graphene-sqlalchemy/pull/87. ```python class ReporterType(SQLAlchemyObjectType): class Meta: model = Reporter class Mutation(graphene.ObjectType): createReporter = create(ReporterType) query = ''' mutation createReporter{ createReporter (firstName: "ABC", lastName: "def") { firstName, lastName,...

1) I think it should be enhanced with @qubitron and @danaronson comments. 2) I won't write those enhancements because I don't use GraphQL anymore at the moment.

There's only an `update_all` mutation missing I think now. Could you review this pull request ? Maybe it requires some documentation update too ?

I've actually abandonned trying to implement a GraphQL service with Python :(. (switched back to REST and Spring/Kotlin)

Workaround for this issue: disable `node/no-missing-import` rule and use [eslint-plugin-import](https://www.npmjs.com/package/eslint-plugin-import) with [eslint-import-resolver-typescript](https://github.com/alexgorbatchev/eslint-import-resolver-typescript).

> I think the proper move would be to implement calling Keycloak's authorization API ourselves instead of relying on their official Node.js adapter. Maybe this code should go in another...

@Poky85 It seems to already support this behavior.

I run v3.0.0, here's my configuration file. My main language is French. ```javascript module.exports = { options: { ns: ['app'], defaultNs: 'app', removeUnusedKeys: true, sort: true, func: { list: ['i18next.t',...

@Poky85 I still have issues in some cases (plurals). It seems https://github.com/i18next/i18next-parser works better, you should have a look.