Closed rkrishnasanka closed 2 months ago
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 | Jul 12, 2024 0:14am |
Sent you a couple thoughts on discord
3. Ensuring that all type structs are PascalCase rather than camelCase since it messes up exports and makes the code hard to read since there is no difference in the instance names and the typedef. This also has the advantage of making sure that all teh structs are available outside the package scope
let me know your thoughts on this since "not exposing" the structs outside the package scope was the point of keeping them camelCase. The idea is that those structs etc are part of the internal API and should not be exposed as they would unnecessarily need to be included in the backward compatibility guarantee slowing down development and also bloating the api documentation.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.
:white_check_mark: rkrishnasanka
:x: deepsource-io[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.
@dosco I know this took a long time but I basically undid all the public structs and helped rename a lot of the variables to get a better idea about the flow.
If this is good, I'll restart the multischema support, we definitely need it on our end
Thats a huge PR did you manually add these comments or is there a tool that helps?
The code currently is hard to work with because of the lack of documentation, the crazy number of features pack in and usage of shorthand variables.
This PR tries to improve the situation for the following scenarios: