Comments (3)
I agree, no point declaring the name twice.
from lighthouse.
I believe the original thought behind it was that the name in the schema file would be the name of the field, while the name in the class would be the name of the GraphQL Type.
However, I do agree that automating this would make the schema file much cleaner. We could make the name optional in the schema (like your example) and default to the (camel-cased) name from the class instance. I actually did something like this in the Connection Registrar (which is a bit of a mess at the moment).
I'll try to get this going later today. I don't think it requires much work, just some defaults in the method signatures and then check if you only have a namespace when registering. Thanks @hailwood!
from lighthouse.
v2.0 uses schema files so no need to register with names anymore!
from lighthouse.
Related Issues (20)
- Programmatically defined types cannot be found or overwrited while parsing .graphql file HOT 3
- @guard directive in fields but I always get "Unauthenticated" error. HOT 1
- Multiple queries / mutations in single request stop at first error HOT 3
- I faced issue lighthouse middleware HOT 1
- work with Multiple database connection HOT 1
- NOT_LIKE operator not working HOT 1
- ебаные пидорасы
- Directives for root types HOT 3
- Schema cache leaks memory with Laravel Octane HOT 1
- I have problems with many-to-many connections
- GraphQL integration in Laravel Repository Pattern
- Can not solve multiple file upload
- [FEDERATION] error SATISFIABILITY_ERROR when check the schema HOT 2
- `@in` directive breaks if client sends null HOT 1
- "No query results for model [App\\Models\\Permission]." using @create mutation HOT 4
- When using throttle directive how can the client be informed when they can retry again etc. HOT 3
- `@can` directive improvements HOT 1
- Only allow deletion of related models in nested mutations
- `@can` with `injectArgs: true` doesn't inject args passed as variables HOT 3
- laravel lighthouse graphql getting error Content-Type multipart/form-data HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lighthouse.