Search Release Notes

Inspiration

I'm a Neo4j Ninja. I check the release notes frequently. I was having trouble remembering which version was released, and finding the timeline of what bugs and features were added.

What it does

The "simple release note" is simple, but it is useful if you forget, or if you want to see a certain category in a time line.

How we built it

We started by migrating the release notes to Neo4j. Next, I checked the connections in GraphQL and modified the graph model. ”GRANDstack” is heavy for my app, and ”create-react-app + apollo/client graphql” gave me a lot of warnings and I had trouble choosing which one to use.

Challenges we ran into

• GraphQL Client/Server
• GRANDstack

Accomplishments that we're proud of

I now understand the GraphQL environment and language, which is completely different from before.

What we learned

• GRANDstack
• create-react-app + apollo/client graphql
• GraphQL Qurty

The GRANDstack may be less effective for small applications, but I think that simple inquiries will be effective when we start handling many devices.

What's next for Search Release Notes

I hope to add voice recognition in the next release. "What has been recently added in Cypher?" This time, importing the release notes was not automatic; there was a manual process to sort out whether a bug was a feature or a fix, fixed or otherwise. Next time, I'd like to make this automatic as well.

I would rather you provide the GraphQL Endpoint for the release notes.

Built With

• grandstack
• graphql
• graphqlplayground
• neo4j