Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #74
Closed
Open
Issue created Mar 20, 2019 by Jaden DIEFENBAUGH@jdiefenbaughContributor

Update the schemas to better reflect parameter type support in different objects

See beat.editor#205 (comment 40301)

The issue we found first is that the algorithm editor's parameter logic doesn't actually support complex types, but the algorithm schema indicates support. See the algorithm schema, algorithm/common.json:80:

 80     "parameter": {                                                                                                                                                        
 81       "type": "object",                                                                                                                                                   
 82       "properties": {                                                                                                                                                     
 83         "type": { "$ref": "../common/1.json#/definitions/basetype" },                                                                                                     
 84         "default": { "$ref": "../common/1.json#/definitions/value" },                                                                                                     
 85         "description": { "type": "string" }                                                                                                                               
 86       },                                                                                                                                                                  
 87       "required": [                                                                                                                                                       
 88         "type"                                                                                                                                                            
 89       ]                                                                                                                                                                   
 90     },

The type field references the basetype types, which includes complex types, but the editors (beat.web & beat.editor) don't actually support complex types for algorithm parameters.

I'll be looking through the other schemas and will update this issue with other things I find, if any.

EDIT: didn't find anything else in the other objects' schemas parameter definitions

Edited Mar 20, 2019 by Jaden DIEFENBAUGH
Assignee
Assign to
Time tracking