-
Notifications
You must be signed in to change notification settings - Fork 1
Simplify Keys and ResultMap structs #2
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
base: master
Are you sure you want to change the base?
Conversation
|
Thanks for the pr. I’m currently juggling a few things but I’ll look over it in the coming days. |
|
After looking at some errors, decided to use Keys as originally defined...did find some interesting enhancements in the process though... |
|
@luisjakon if you have any ideas that differ from the current PR please open a second PR. Thanks for the contributions BTW! |
|
The ideas are somewhat intertwined. While trying to simplify the structs I came across an enhancement to the LoadMany cache retrieval code which I unintentionally embedded onto this PR, but it works. Have a look at the dataloader.LoadMany(...) function. |
The idea is to remove hard dependencies on strings and use these structs a close to bare metal as possible.
It may be also possible to remove dependence on defined methods for internal calls in the future since the new definitions are simple native arrays and maps in go. The benefit here is that downstream consumers can simply choose to use them as such through simple conversions.