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.

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

run list by channel server side (GQL) #1545

Closed
trilopin opened this issue Nov 4, 2022 · 0 comments · Fixed by #1561
Closed

run list by channel server side (GQL) #1545

trilopin opened this issue Nov 4, 2022 · 0 comments · Fixed by #1561
Assignees

Comments

@trilopin
Copy link
Contributor

trilopin commented Nov 4, 2022

Prepare service and store layer to be able to get all the runs linked to a channeled.

At graphql side we have to decide if we evolve the runs root resolver to accept channelID as criteria (and make optional participantOrFollowerID?) or to create another root resolver.

Current:

	runs (participantOrFollowerID: $userID, teamID: $teamID, sort: "name", statuses: ["InProgress"]){
		id
		name
		isFavorite
		playbookID
		ownerUserID
		participantIDs
		metadata { followers }
	}
func (r *RunRootResolver) Runs(ctx context.Context, args struct {
	TeamID                  string `url:"team_id,omitempty"`
	Sort                    string
	Statuses                []string
	ParticipantOrFollowerID string `url:"participant_or_follower,omitempty"`
}) ([]*RunResolver, error) {
...
@trilopin trilopin changed the title run list by channel server side run list by channel server side (GQL) Nov 6, 2022
@crspeller crspeller self-assigned this Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants