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

Hide underlying graph implementation on Browse panel #115

Closed
lvca opened this issue Aug 23, 2014 · 3 comments
Closed

Hide underlying graph implementation on Browse panel #115

lvca opened this issue Aug 23, 2014 · 3 comments
Assignees
Milestone

Comments

@lvca
Copy link
Member

lvca commented Aug 23, 2014

When you execute a query you can see fields like out_Like or in_IsFriendOfthat is not really helpful because on query we always suggest to use in(), out() and both() functions.

So here my proposal: when the result set contains something "graph", Studio should display above properties is better way.

We could create a super header in the result table with 3 sections:

  • Properties, where to put all the properties
  • In, where to put all the incoming relationships
  • Out, where to put all the outgoing relationships

Example (sorry for this piece of ascii art):

PROPERTIESINOUT
namesurnameFriendOfWhateverFriendOfFavorites
JayMiner#13:33[#21:32,#23:2342][#16:34][#23:332,#232,4545]
@lvca lvca added this to the 2.0rc1 milestone Aug 23, 2014
@lvca
Copy link
Member Author

lvca commented Aug 23, 2014

@maggiolo00 WDYT?

@kwoxer
Copy link

kwoxer commented Aug 25, 2014

For me that sounds great. Really appreciate that. And if possible save the ordering of the elements.

wolf4ood added a commit that referenced this issue Aug 27, 2014
@wolf4ood
Copy link
Member

Implemented Metadata Properties In Out.
To close this issue implements also Relationship

@wolf4ood wolf4ood closed this as completed Sep 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants