Skip to content

Conversation

bwaidelich
Copy link
Member

@bwaidelich bwaidelich commented Mar 30, 2023

usage

# get first reference instance
${q(node).references().get(0)}

# get first reference name
${q(node).references().get(0).name}

# get property of the first reference itself
${q(node).references("someReferenceName").referenceProperty("someReferenceProperty")}

# get property of first referenced node
${q(node).references().nodes().property("someNodeProperty")}

# the same API for back references
${q(node).backReferences("someReferenceName").referenceProperty("someReferenceProperty")}

Resolves: #4144

## usage

    ${q(node).references().get(0)}
    ${q(node).references("someReferenceName").property("somePropertyName")}
    ${q(node).backReferences("someReferenceName").property("somePropertyName")}

Resolves: #4144
@bwaidelich bwaidelich marked this pull request as draft March 31, 2023 08:42
@bwaidelich
Copy link
Member Author

bwaidelich commented Mar 31, 2023

TODO

  • dedicated referenceProperty operation (revert property operation changes)
  • new nodes operation

@bwaidelich bwaidelich marked this pull request as ready for review April 1, 2023 10:10
@skurfuerst
Copy link
Member

@bwaidelich don't we still need the nodes() FlowQuery operation? otherwise looks good :)

@bwaidelich
Copy link
Member Author

@skurfuerst doh, you're right. I'll take care!

@bwaidelich bwaidelich enabled auto-merge April 2, 2023 15:36
@skurfuerst skurfuerst disabled auto-merge April 2, 2023 18:14
@skurfuerst skurfuerst enabled auto-merge April 2, 2023 18:15
@skurfuerst skurfuerst merged commit 0d5080e into 9.0 Apr 2, 2023
@skurfuerst skurfuerst deleted the feature/4144-references-flowquery-operation branch April 2, 2023 18:15
@skurfuerst skurfuerst added this to the 9.0 (ES CR) milestone Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants