Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

Invitation to contribute to the (new) Graql repository #40

Open
haikalpribadi opened this issue Feb 17, 2019 · 2 comments
Open

Invitation to contribute to the (new) Graql repository #40

haikalpribadi opened this issue Feb 17, 2019 · 2 comments

Comments

@haikalpribadi
Copy link

Hi @BFergerson - I hope you're doing well! Thank you so much for developing a JetBrains plugin for Graql - the community loves it!

Graql also has its own repository now:

https://github.com/graknlabs/graql (thank you for the star! 😉)

This would allow Graql to have a development cycle independent from Grakn, but also centralise the codebase for various Graql implementations and plugins under one place. This would allow us to maintain the language for all end-users in a synchronised and reliable way (always updated and always tested).

How would you feel about contributing JetBrains Graql plugin to the new Graql repo and become one of the maintainers and contributors to the repository? :) I'm sure the community would love it!

@BFergerson
Copy link
Owner

BFergerson commented Feb 17, 2019

Hey @haikalpribadi, I would love to contribute to the new repository. I wasn't planning on updating this project till after the release of Grakn 1.5 though. There are a couple of bugs (vaticle/typedb#4349, vaticle/typedb#4447) that are blocking me from spending time on my Grakn projects right now so I haven't been writing too much Graql :P.

After the release of Grakn 1.5 I think it would be a good idea to transfer this project to the Graql repository. It doesn't use the official Graql grammar file so it would be a good time to make that switch too. I've always considered that to be the weakest link in this project.

@haikalpribadi
Copy link
Author

Thanks, @BFergerson - that sounds great!

Regarding grakn issue #4349: we now have a new Graql Filtering (sort, offset, limit) implemented in grakn PR #4910. I believe the issue should be fixed now.

Regarding grakn issue #4447: I've prioritised this and assigned to myself. Thank you for bumping it up!

And indeed, having all language plugins be based on the native Graql grammar would definitely be an improvement! 🙂 Let's revisit this topic once we release Grakn Core v1.5.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants