Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.core
beat.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.corebeat.core
  • Issues
  • #74

Closed
Open
Opened Mar 20, 2019 by Jaden DIEFENBAUGH@jdiefenbaugh
  • Report abuse
  • New issue
Report abuse New issue

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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
bug
Assign labels
  • View project labels
Reference: beat/beat.core#74