Roadmap

[lvarayut]

Update: We stop supporting Yeoman for now, until we can find a good way to maintain it in our project, see more details #72.

Here is all the features planned to be developed. I list them out in order to make it easy for everybody to discuss and participate in the project. These features could be changed as needed, so don't hesitate to express your ideas. If you wanted to help developing some features, which would be very appreciated, please leave a comment below.

• Example on Heroku @lvarayut
• Official website (gh-pages) @lvarayut
• Yeoman generator @lvarayut
• Integrate css-modules @lexun
• Mutation example @Zenyai
• Flow* @Neitsch
• Data loader* @Neitsch
• Database integration* (MongoDB, MySQL, Postgres, and Cassandra)
• Yeoman sub-generators (Component, Container, Query, Mutation)*
• Testing framework (which one do you prefer: Jest, Mocha, Jasmine, Ava?) @lvarayut
• Server Side Rendering
• JSON Web Tokens* (Implement* Signup and Login pages) - This will be developed after Database integration
• Browsersync

*must be developed in canary branch.

[keon]

This is awesome, thanks for the project!
But why Browserify when you already got webpack?

[keon]

Also when adding database integration, adding all the graphql schema and mongodb (mongoose, likely) schema into one folder seems to be counter intuitive. Why don't we split GraphQL schema into /graphql and database into database or conventionally called model?

So the proposed files structure might look like the one below:

   ├── models                   
   │   ├── index.js 
   │   ├── User.js
   │   └── Feature.js 
   ├── graphql 
   │   ├── schema.graphql
   │   ├── schema.js
   │   └── schema.json 

[lvarayut]

why Browserify when you already got webpack

Thanks for expressing your idea. Browserify was a typo. It meant to be Browsersync instead.

Why don't we split GraphQL schema into /graphql and database into database

Yes, when integrating the MongoDB, I have planned to restructure the schema/query/mutation structures.

[keon]

@lvarayut I can work on MongoDB and Mongoose part
Please refer to my fork to see my proof of concept.
(It might be immature as I am building it while learning graphql)

[lvarayut]

Thanks @KeonKim. That would be great. Don't worry, take your time to learn GraphQL and complete your MongoDB in your fork. I can check it out afterward. However, you might also consider that do we really need to use Mongoose or just the simple MongDB driver is enough. Also, JWT is the preferable choice for authentication.

[AhmadEl-Banna]

@lvarayut @KeonKim if you decide to go with MongoDb and mongoose ,have a look at https://github.com/RisingStack/graffiti-mongoose,
I think it will remove a lot of redundant work with graphQL

[lvarayut]

@AhmadEl-Banna, Thanks for your suggestion. @KeonKim has suggested it also. I'll take a look at it.

[sachgits]

Hi everyone love the progress been using these and after checking the Roadmap issue i wondered why not contribute to these. and by look of who is working on what seems like the JWT is open as it waits for the mongoDB (mongoose) database. i don't know much yet on JWT but i do research on it and take part on the login and signup pages that's if am welcome hahaha thanks guys

[lvarayut]

@sachgits, I would say that the JWT should be done after the database integration. If you could, please take a look at the database integration before digging down into JWT.

[sachgits]

@lvarayut ok let me do that also to add i think that they types should have separation inside of schema and with of which Persons Types, Feature Types node definitions and connection definitions should go separately