-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create a more universal method of supporting and retreiving protocol_url
#606
Comments
From @libpitt, potential query to address the first point
|
libpitt
added a commit
that referenced
this issue
Feb 5, 2025
libpitt
added a commit
that referenced
this issue
Feb 5, 2025
libpitt
added a commit
that referenced
this issue
Feb 5, 2025
libpitt
added a commit
that referenced
this issue
Feb 6, 2025
libpitt
added a commit
that referenced
this issue
Feb 6, 2025
libpitt
added a commit
that referenced
this issue
Feb 7, 2025
libpitt
added a commit
that referenced
this issue
Feb 10, 2025
libpitt
added a commit
that referenced
this issue
Feb 10, 2025
libpitt
added a commit
that referenced
this issue
Feb 11, 2025
libpitt
added a commit
that referenced
this issue
Feb 11, 2025
… remove comments that no longer apply - #606 621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The two primary issues with
protocol_url
is that it lives inside ofActivity
and it isn't always necessary.We currently have to specially handle this property in these main locations:
app_neo4j_queries.py
where we iterate over the result of the initial query then append the result ofget_activity_protocol
which is another Neo4j queryThe text was updated successfully, but these errors were encountered: