Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Question or idea Button #122

Open
2 tasks done
ElecTwix opened this issue Jan 9, 2024 · 2 comments
Open
2 tasks done

Bug: Question or idea Button #122

ElecTwix opened this issue Jan 9, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@ElecTwix
Copy link
Contributor

ElecTwix commented Jan 9, 2024

Describe the bug

While Creating Issues
The Question or idea button redirects to void

https://github.com/surrealdb/surrealdb.go/blob/main/.github/ISSUE_TEMPLATE/config.yml

Steps to reproduce

  1. go to the issues tab
  2. create a new issue
  3. click on Question or idea labeled button
  4. Get 404

Expected behaviour

to not redirect to void

SurrealDB version

non-related

Contact Details

root@electwix.dev

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct
@ElecTwix ElecTwix added the bug Something isn't working label Jan 9, 2024
@ElecTwix
Copy link
Contributor Author

ElecTwix commented Jan 9, 2024

Also maybe we can create a discussion board for the go driver repo.
I wanted to discuss the new direction of driver will go and when these major changes will occur.

@gedw99
Copy link

gedw99 commented Apr 4, 2024

I think a discussion board is useful because of this golang package being at such an early stage.

I have many things I would like to discuss with regarding to integration with the other features of Surreal DB. CDC aspects with regarding to Live feeds, TiKV for clustering, etc. Thats just a small gamut of the things.

Even migrations is missing.

I also saw that there is talk of supporting sql, like what has started here: https://github.com/NoBypass/surgo

By having a discussions and roadmap, there will be less splintering / fragmentation, like what is happening with surgo, and devs can then work together to bring new features into the main code base, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants