You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following #143, we can create delegations using participant IDs (for pre-existing participants) in much the same way as with participant emails. Despite permitting participant IDs in the absinthe deleteDelegation mutation, however, we have no matching action(s).
This development should also include the voting results updates (on delegation deletions) that are covered in #44.
The text was updated successfully, but these errors were encountered:
Makes sense. I'd like to discuss having separate clauses for each scenario, though. And for the each of the error handling scenarios.
I had another look at the delegation creation resolver, and now it feels like it's doing a lot there. Same for the args validator - feels like it could be broken into different clauses as well? Maybe we can pair on this
Following #143, we can create delegations using participant IDs (for pre-existing participants) in much the same way as with participant emails. Despite permitting participant IDs in the absinthe deleteDelegation mutation, however, we have no matching action(s).
This development should also include the voting results updates (on delegation deletions) that are covered in #44.
The text was updated successfully, but these errors were encountered: