-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
FEATURE: Improved FlowQuery find operations for Neos 9 #5434
Labels
Comments
mficzel
changed the title
FEATURE: Improved FlowQuery operations for Neos 9
FEATURE: Improved FlowQuery find operations for Neos 9
Jan 10, 2025
mficzel
added a commit
to mficzel/neos-development-collection
that referenced
this issue
Jan 10, 2025
`findByCriteria` allows to query the subgraph below the contextNode with the following arguments: - string | null: nodeTypefilter - string | null: propertyValueCriteria - object{offset?:int, limit?:int} | null: pagination `findByIdentifier` will find a node with the given aggregate id in the subgraph defined by the contextNode: - string: nodeAggregateId Resolves: neos#5434
6 tasks
mficzel
added a commit
to mficzel/neos-development-collection
that referenced
this issue
Jan 10, 2025
`findByCriteria` allows to query the subgraph below the contextNode arguments: - string | null: nodeTypefilter - string | null: propertyValueCriteria - object{offset?:int, limit?:int} | null: pagination `findByIdentifier` will find a node with the given aggregate id in the subgraph defined by the contextNode arguments: - string: nodeAggregateId Resolves: neos#5434
mficzel
added a commit
to mficzel/neos-development-collection
that referenced
this issue
Jan 10, 2025
`findByCriteria` allows to query the subgraph below the contextNode arguments: - string | null: nodeTypefilter - string | null: propertyValueCriteria - object{offset?:int, limit?:int} | null: pagination `findByIdentifier` will find a node with the given aggregate id in the subgraph defined by the contextNode arguments: - string: nodeAggregateId Resolves: neos#5434
mficzel
added a commit
to mficzel/neos-development-collection
that referenced
this issue
Jan 10, 2025
`findByCriteria` allows to query the subgraph below the contextNode arguments: - string | null: nodeTypefilter - string | null: propertyValueCriteria - object{offset?:int, limit?:int} | null: pagination `findByIdentifier` will find a node with the given aggregate id in the subgraph defined by the contextNode arguments: - string: nodeAggregateId Resolves: neos#5434
mficzel
added a commit
to mficzel/neos-development-collection
that referenced
this issue
Jan 10, 2025
`findByCriteria` allows to query the subgraph below the contextNode arguments: - string | null: nodeTypefilter - string | null: propertyValueCriteria - object{offset?:int, limit?:int} | null: pagination `findByIdentifier` will find a node with the given aggregate id in the subgraph defined by the contextNode arguments: - string: nodeAggregateId Resolves: neos#5434
mficzel
added a commit
to mficzel/neos-development-collection
that referenced
this issue
Jan 10, 2025
`findByCriteria` allows to query the subgraph below the contextNode arguments: - string | null: nodeTypefilter - string | null: propertyValueCriteria - object{offset?:int, limit?:int} | null: pagination `findByIdentifier` will find a node with the given aggregate id in the subgraph defined by the contextNode arguments: - string: nodeAggregateId Resolves: neos#5434
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this topic?
Description
The syntax of find and children operations is quite ambigious and maps pooly to the new CR API.
Possible Solution
Since this is hard to fix new flowQuery operations that are modeled for the cr could help.
deprecate
find
in favor ofdeprecate
children
in favor ofThe text was updated successfully, but these errors were encountered: