Skip to content

Conversation

realFlowControl
Copy link
Contributor

This pull request makes the ClassNameMapper instance injectable via setter in the SchemaFactory. If not injected, everything behaves as before this PR.

@moufmouf
Copy link
Member

moufmouf commented Oct 8, 2019

Hey @flow-control ,

Looks good to me! Quite impressed with your PR ;)

Would you mind adding just a call to the setClassNameMapper method in the SchemaFactoryTest to fix code coverage?

Also, just out of curiosity, in what scenario did you need to inject a new ClassNameMapper?

@realFlowControl
Copy link
Contributor Author

Hey @moufmouf,

we @OXID-eSales are building a GraphQL API on top of our e-commerce system, which will not be part of the core distribution but installable as a plugin. This means, that projects composer.json will not have the namespaces and paths to the GraphQL types, queries, mutations, ...

I will fix the code coverage and btw.: thanks for this very awesome library 👍

/Flo

@moufmouf
Copy link
Member

moufmouf commented Oct 9, 2019

Thanks a lot! 👍

@moufmouf moufmouf merged commit 6dad76e into thecodingmachine:master Oct 9, 2019
@realFlowControl realFlowControl deleted the make-classNameMapper-injectable branch October 9, 2019 07:28
realFlowControl added a commit to realFlowControl/graphqlite that referenced this pull request Oct 9, 2019
realFlowControl added a commit to realFlowControl/graphqlite that referenced this pull request Oct 11, 2019
moufmouf added a commit that referenced this pull request Oct 14, 2019
…able-in-3.0

Backport classNameMapper injectability from #144 to graphqlite v3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants