Max (elmasse) brought up this topic:
We could set up a separate repository to create a neo.mjs middleware using nodejs & GraphQL.
Take a look at:
https://graphql.org/graphql-js/
https://medium.com/codingthesmartway-com-blog/creating-a-graphql-server-with-node-js-and-express-f6dddc5320e1
This is an epic and probably involves a lot of work.
In short: neo.mjs should have a socket connection to the node server, probably using a custom API.
Schemas defined in the middleware could optionally automatically create models on the client side as well as the other way around. Changes to the data of a middleware schema should automatically update the store data of a bound client-side store as well as the other way around.
Would help for testing buffering of remotely loaded grids & tables.
I could definitely use feedback on this one!
Max (elmasse) brought up this topic:
We could set up a separate repository to create a neo.mjs middleware using nodejs & GraphQL.
Take a look at: https://graphql.org/graphql-js/
https://medium.com/codingthesmartway-com-blog/creating-a-graphql-server-with-node-js-and-express-f6dddc5320e1
This is an epic and probably involves a lot of work.
In short: neo.mjs should have a socket connection to the node server, probably using a custom API.
Schemas defined in the middleware could optionally automatically create models on the client side as well as the other way around. Changes to the data of a middleware schema should automatically update the store data of a bound client-side store as well as the other way around.
Would help for testing buffering of remotely loaded grids & tables.
I could definitely use feedback on this one!