Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.editor
beat.editor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • 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.editorbeat.editor
  • Issues
  • #161

Closed
Open
Opened Sep 26, 2018 by Flavio TARSETTI@flavio.tarsetti
  • Report abuse
  • New issue
Report abuse New issue

[validation] types and values for parameters not properly checked in editor/ second issue old value saved

@jdiefenbaugh : The editor presents some validation bugs

The editor seems to have unexpected behavior for validation of parameters.

A string value could be saved in a int8, and this is valid and could be saved in the json file.

A second issue comes from the fact that all parameters have their old value saved somewhere in the props or state history.

For example if we suddenly decide to change the parameter type from "string" to "int", the value "helloworld" will be kept as the value for the "int"

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
3
Labels
bug confirmed v1
Assign labels
  • View project labels
Reference: beat/beat.editor#161