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

With aql template strings, I can use Document/EdgeCollections in templates but not Graphs. #740

Closed
earslap opened this issue Jul 23, 2021 · 2 comments
Labels
Feature Request Request for new functionality to be added to the driver. fixed Issue has been resolved but remains open due to a pending release.

Comments

@earslap
Copy link

earslap commented Jul 23, 2021

Is this intended? Inside ${} within an aql template, I can refer to document collection objects directly and the templating system does its interpolation job, but if I use a Graph object inside ${} the queries fail. I have to explicitly use ${myGraph.name} and refer to it by name for the query to work. Is this intended behavior?

@alexgorbatchev
Copy link

Can also confirm this. Same question. Feels unintentionally broken.

@pluma pluma added the Feature Request Request for new functionality to be added to the driver. label Sep 30, 2021
@pluma pluma added the fixed Issue has been resolved but remains open due to a pending release. label Oct 20, 2021
@pluma pluma closed this as completed in ea0029f Oct 20, 2021
@awlayton
Copy link

This issue seems to be back?

If I do ${myGraph} it gets a key like @value0 but the query fails unless I change it to value0 manually, or use ${myGraph.name}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Request for new functionality to be added to the driver. fixed Issue has been resolved but remains open due to a pending release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants