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.

Sign up for GitHub

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

Jump to bottom

Feature Design - Change response structure to simplify hits.edges.nodes #845

Open
joneubank opened this issue Aug 14, 2023 · 0 comments
Open

Feature Design - Change response structure to simplify hits.edges.nodes #845

joneubank opened this issue Aug 14, 2023 · 0 comments
Assignees
@justincorrigible
Labels
design Specs are undergoing ui design documentation Help docs are needed for this/writing docs needed refactor

Comments

@joneubank
Copy link
Contributor

Detailed Description

The use of hits.edges.nodes is cumbersome and unnecessary, and definitely confusing especially for new devs. This is a relic of an old recommendation for GQL response structure.

We would like to propose a new response structure and use the upcoming release of Arranger 3 to use the new structure. This ticket is a stub to provide a place to document and discuss a new alternative approach.
@joneubank joneubank added documentation Help docs are needed for this/writing docs needed design Specs are undergoing ui design refactor labels Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justincorrigible justincorrigible

Labels
design Specs are undergoing ui design documentation Help docs are needed for this/writing docs needed refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@justincorrigible @joneubank