Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • slapos slapos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 129
    • Merge requests 129
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • slaposslapos
  • Merge requests
  • !421

change instance-erp5-input-schema.json without result json document change.

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Boris Kocherov requested to merge bk/slapos:json_schema_changes into master Oct 12, 2018
  • Overview 7
  • Commits 1
  • Pipelines 0
  • Changes 1

Hello @vpelletier

i am not sure i correctly understand this slapos schema but i wanted to give an example how to properties in json schema can be connected to each other. could you please review.

the purpose of mr: user has one choice instead of two choices in ui. before change type field and server field were not connected and user had to select type independently of server select.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: json_schema_changes
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7