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: Add .fetched method to related node to determine if the related node(s) has been fetched #245

Open
FragmentedPacket opened this issue Jan 21, 2025 · 0 comments
Open

feature: Add .fetched method to related node to determine if the related node(s) has been fetched #245

FragmentedPacket opened this issue Jan 21, 2025 · 0 comments
Labels
state/backlog This issue is part of the backlog type/feature New feature or request

Comments

@FragmentedPacket
Copy link
Contributor

Component

Python SDK

Describe the Feature Request

Reading the Querying data guide, there is no way to distinguish if the related node has been fetched or not. It would be helpful to understand if the node has been initialized and fetched.

This is should help clarifying the different states of a related node.

Describe the Use Case

Before accessing the peer/peers on a related node, it would be nice to have an attribute to call to understand whether or not peer has been fetched.

Additional Information

No response
@FragmentedPacket FragmentedPacket added the type/feature New feature or request label Jan 21, 2025
@exalate-issue-sync exalate-issue-sync bot added state/needs-triage state/backlog This issue is part of the backlog state/need-triage This issue needs to be triaged and removed state/needs-triage state/need-triage This issue needs to be triaged labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
state/backlog This issue is part of the backlog type/feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FragmentedPacket