Mirror of forum.nim-lang.org

3937 :: https://github.com/jdhorwitz/NimQL

• markfirmware (orginal) [2018-06-18T09:00:49+02:00] view original

  What is GraphQL? Is it https://graphql.org ?

  That web page is too long so I didn't read it. Also put off by their confusion between an api and a web json/http interface.

  Anyways a browser search on nimql brings up https://github.com/barcharcraz/nimql

  I vote to rename your repo to nimgraphql (all lower case.)

  ---

  Is graphql a de facto industry standard? Is there a feasible path to where it can be used to query nimble.directory for all procs that have arguments that include exactly two string arguments and return a whole number? If the answers are affirmative then I can help.

  Your appreciation for help and guidance is much appreciated.

  Kindest regards, Mark

---

• mratsim (orginal) [2018-06-18T09:59:43+02:00] view original

  You should probably create an issue on the repo directly for the first part of your message.

  Regarding industry standard, around me I would say yes. Managing REST endpoints seems to be a major pain point.

  For nimble.directory you can ask @FedericoCeratto via an issue on his repo https://github.com/FedericoCeratto/nim-package-directory. As always PR welcome ;).

---

• federico3 (orginal) [2018-06-18T17:59:09+02:00] view original

  GraphQL is still fairly new, and not very popular when compared to SQL and REST. As a graph query language, it provides moderate benefits for your use case in contrast to REST/JSON. The package directory started supporting searching for symbols recently - adding the search capability you describe would require some more clever indexing. If there's interest from other users I'll be happy to consider it.

---