Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • X XML-To-Blockly
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • XML-To-Blockly
  • Issues
  • #9

Closed
Open
Created Aug 10, 2016 by Marek Szuba@mksContributor

Incorrect name in for repeated magic block

Created by: anujk14

A choice/interleave that has a one/zeroOrMore as its child gets assigned the block number as part of its notch label and childrenInfo list. If this one/zeroOrMore turns out to be a repeated child for which a block has already been created, we get an incorrect notch label as well as childrenInfo list (since currently childrenInfo uses pretty names) .

Example to test bug : bug_05_choice_having_oneOrMore_having_wrong_name.rng

Assignee
Assign to
Time tracking