-
Notifications
You must be signed in to change notification settings - Fork 69
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
What is the idea of how to read values values out of PackStreamStruct? #244
Comments
Thanks so much for reporting to us! |
Thank you Zhen,
However, the "Tests" project runs fine. |
@flq Yeah, IT and TCK tests requires aws to download a server to run all tests unless you have already downloaded a server by running tests before. You could probably run most of IT and TCK tests if you have a community server in the path I will also fix this by allow a user to provide a file path to download server in boltkit later. Be free to start a PR and send us a CLA, then your PR will be built by our build server. |
Looks like the PR is merged, and it is already in the Nuget - I think that is nothing short of awesome, folkes. Thank you! |
Okay...um, color me confused. I look at the Driver code, it does not have Is the code not in the nuget yet? |
I just tested with 1.5.0-rc2 and it is working as expected with nested nodes and relationships coming out as desired, or arbitrary values as a dictionary. From my point of view this could be closed. Thank you very much, people 🥇 |
Consider the following statement:
Here the products key will point to a
List<object>
whose elements areNode
s, fair enough.Now, suppose I also need relationship info and do something like this:
What I now get is
And here I cannot sensibly access the values of rel and product anymore because the value is represented with an internal object.
If you tell me that this is a fairly stable API I can drill holes into it to extract the values, but maybe you tell me that you will actually make those items public?
Looking forward to any pointers
The text was updated successfully, but these errors were encountered: