Comments (3)
Hi,
I totally aree with the benefits. I also think it would be a good idea to separate it into its own nuget package and I would be definetly looking forward to our collaboration on this.
Just now I created a repository where I tried to create a package containing standalone parser and its tests. I reused the approach that Newtonsoft.Json uses to create their multiplatform nuget package.
https://github.com/mkmarek/graphql-dotnet-parser
I also tried a test deploy to myget and it seems that it works nicely.
https://www.myget.org/feed/graphqlcore-ci/package/nuget/GraphQLParser
Also since we both are gonna be dependent on this package then it would make sense to make it more futureproof in a sense that it wouldn't be bound on our user accounts (specifically mine in this case). I would propose moving it into your graphql-dotnet organization.
Then it would be a matter of setting up CI and autodeploy.
Also when it comes to how much is the parser functionality complete. The parser itself can parse everything from the current GraphQL spec. Only the Ast visitor doesn't support visiting all the different nodes. I was adding them based on the need of different components mainly while implementing validation.
from graphql-dotnetcore.
I guess we can close this issue and continue in graphql-dotnet/parser#1?
from graphql-dotnetcore.
Awesome - looks pretty good. I've invited you to the graphql-dotnet org so we can transfer ownership there.
I did a spike of integrating the parser into my project already and it is working well.
from graphql-dotnetcore.
Related Issues (20)
- Implement graphql subscriptions HOT 1
- Validation ast visitor should support introspection types HOT 1
- Implement GraphQL union types HOT 1
- Any plans for relay integration? HOT 2
- Support for nullable enums
- Fix null variables
- Migrate build process to MSBuild.net Core
- Add GraphQLID scalar type HOT 1
- Unique directives per location validation rule HOT 1
- Resolve type validation on subscriptions HOT 1
- Single Field Subscriptions validation rule HOT 1
- Add location information to graphql errors HOT 1
- Add path information to graphql errors HOT 1
- Better subscription support and demo HOT 1
- Initial support for @defer, @stream, and @live
- Create possibility to set description to to field in GraphQLObject HOT 1
- Create possibility to deprecate field HOT 1
- Create possibility to specify default value for field arguments HOT 1
- Example working with EF Core 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 graphql-dotnetcore.