Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • V vf-apps
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Value Flows
  • VF App Specs
  • vf-apps
  • Issues
  • #5

Closed
Open
Created Nov 07, 2019 by pospi@pospiOwner

Validation logic

Beyond schema validation we need to define all the custom validation rules that apply to records at the API boundary. This includes validation for 'either' fields as well as any other custom dependencies, existence checks and domain-specific constraints that need to be imposed in order for requests to be considered valid.

Starting with the observation, planning & specification records (in that order) would be optimal in terms of informing HoloREA's development as it progresses.

Assignee
Assign to
Time tracking