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

Support for mutiple schemas #491

Draft
wants to merge 17 commits into
base: master
Choose a base branch
from

Conversation

rkrishnasanka
Copy link
Contributor

Changes:

  • Updated the set search_path parameter for postgres to parse from th…e yaml (an array of strings)
  • Updated a variable c which a copy of a configuration file to make the code more readable.

I'm starting to make some changes to the code documentation here. I'm including a bit of refactoring to make sure that things are more readable.

- The code extensively uses the short variable names to the detriment of the readability. This compounds the problem of not having enough code documentation.

- While golang recommends short variable names, the intention is to avoid long nested function calls and to avoid diverting the attention from the main logic of the program. However, even the main logic variables have really short names making it almost impossible to read.
Copy link

vercel bot commented Apr 7, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
graphjin ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 10, 2024 0:39am

rkrishnasanka and others added 14 commits April 12, 2024 15:25
1. Changed all type structs were Pascal Case
2. Expanded 2-3 character field names for structs
3. Tried removing redundant functions
* Updated the  basic documentation example

* Improving code clarity
I'm starting to make some changes to the code documentation here. I'm including a bit of refactoring to make sure that things are more readable.

- The code extensively uses the short variable names to the detriment of the readability. This compounds the problem of not having enough code documentation.

- While golang recommends short variable names, the intention is to avoid long nested function calls and to avoid diverting the attention from the main logic of the program. However, even the main logic variables have really short names making it almost impossible to read.

* Incremental renaming of variables in intro.go
…aphjin queries (dosco#468)

* Updated the  basic documentation example

* Updated addTable function to create a new variable that would create the type that has not_null for id in the scenario where we query by ID

* Update intro.go

* Update intro.go

* Update intro.go

---------

Co-authored-by: Spacy <[email protected]>
…e yaml (an array of strings)

* Updated a variable c which a copy of a configuration file to make the code more readable.
Copy link

vercel bot commented Apr 15, 2024

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

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

Successfully merging this pull request may close these issues.

2 participants