Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,931
    • Issues 34,931
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,280
    • Merge Requests 1,280
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #258969

Closed
Open
Opened Sep 30, 2020 by Jan Provaznik@jprovaznikMaintainer

GraphQL: consider adding a helper method for defining negated arguments

We settled on the format of passing negated arguments (!41350 (merged)). There are various options to defined the list of arguments which can be negated. One of elegant options which was suggested by @alexkalderimis in !41350 (comment 416036126) is having a helper resolver method which would limit the size of boilerplate for negated args definition.

Because at the moment of documenting negated args (!41350 (merged)) it wasn't used in the code, we didn't add it into documentation, but it seems to be an elegant solution to consider when anyone will be adding negated args for a resolver.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#258969