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
  • #88

Closed
Open
Opened Nov 20, 2020 by pospi@pospi
  • Report abuse
  • New issue
Report abuse New issue

Add spec for revision handling

Following #87, there needs to be a core specification for handling conflicting data and access to prior revisions in eventually consistent architectures.

All UIs (regardless of whether the backend implements such features) will need to implement these interfaces in order to be considered "fully compatible" with the spec. This implementor burden should be kept as minimal as possible; ergo the smallest number of additional fields and simplest application logic should be favoured.

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