Closed jinjagit closed 3 years ago
Reviewers, please note: I just removed a stray debug comment, as it was somewhat misleading. Thanks.
Also this delegations filtering is a hack that won't scale. If the current api doesn't allow us to give parameters like delegator_email
and proposal_url
in our graphql queries, we need to add that! (in another issue)
Also this delegations filtering is a hack that won't scale. If the current api doesn't allow us to give parameters like
delegator_email
andproposal_url
in our graphql queries, we need to add that! (in another issue)
Agree. See my initial comment in this PR. Main issue here is prioritizing when to do this.
I have included all of @davefrey's suggested changes.
I have also created issue #163 to address the need for a specific absinthe query to facilitate the delegations filtering mentioned in preceding comments.
I think I have satisfied all suggested changes, except regarding my 2 remaining doubts:
EDIT: Now answered. All suggested changes are included.
Continuing work on #9
Check for
delegated_to
session parameter. If not found, then set to appropriate value (if relevant delegation exists), or set to 'none'. Involves querying the api db for a list of delegations, in order to set the appropriate value fordelegated_to
.In future, we may wish to develop a new absinthe query of delegations, where we can search using delegate email and proposal URL to return a single delegation (if found), rather than simply getting a list of all delegations (as in the present solution).