Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
V
vf-graphql
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Value Flows
  • VF Schemas
  • vf-graphql
  • Issues
  • #72

Closed
Open
Opened Mar 05, 2020 by pospi@pospi
  • Report abuse
  • New issue
Report abuse New issue

Agree on API for agent inventory queries

I want to start logging these here to loop in @ivanminutillo as I work through porting Shroom to work on the latest vf-graphql spec. So far it has been minor things like allowing string IDs (in addition to integers) but it will quickly become a discussion about which queries are optimal and easiest to build UIs on top of.

I began with the inventory section of the app. Shroom has Agent.ownedEconomicResources(category: INVENTORY). Here the closest we have is inventoriedEconomicResources().

So the first question is, how to split this up? Separate methods for "owned", "inventoried", "onhand"; or a single query edge for Agent.economicResources that includes a category filter as one of its criteria?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
decision
Assign labels
  • View project labels
Reference: valueflows/vf-schemas/vf-graphql#72