| Summary: | [Refactoring] In some cases moving a package causes the parent package to be removed | ||
|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Navid Mehregani <nmehrega> |
| Component: | Core | Assignee: | Project Inbox <tigerstripe.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | 0.5M0 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
Fixed. |
Build Identifier: Consider the following project structure: MyProject src <- Source folder source <- Package foo <- Package destination <- Package moving foo to destination causes 'source' to be removed! Reproducible: Always Steps to Reproduce: 1. Create a model project 2. Create a package called 'source' in the 'src' folder 3. Create a package called 'destination' in the 'src' folder 4. Create a package called 'foo' under 'source' package 5. Define a class diagram, two entities and an association between the entities under 'foo' 6. In TS explorer, right click on 'foo' > Refactor Model > move. Select 'destination' in the dialog box that pops up > click on OK Expected outcome would be for 'foo' to be moved to 'destination' and 'source' would remain as is. However, 'source' package is removed for some reason!