| Summary: | TS blocks creating a package if a similar artefact name exists in the same directory | ||
|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Chris Hartley <chrhartl> |
| Component: | Core | Assignee: | Project Inbox <tigerstripe.core-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | nmehrega |
| Version: | unspecified | ||
| Target Milestone: | 0.5M0 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Chris Hartley
This has been scheduled for i35. The reason why TS blocks this scenario is because packages are treated just like any other Tigerstripe artifact. We'll need to make a design change in order to resolve this issue, which will imply change to refactoring logic, diagrams, UI, etc... This defect has been moved out of i35 so it can be further discussed before any changes are made. I've decided to mark this defect as won't fix due to the risks involved in making the necessary design changes in Tigerstripe. As stated in my previous comment, packages are treated as regular Tigerstripe artifacts, which is why the tooling prevents an entity artifact to be created under a package of the same name. If this defect is completely blocking you, please re-open it so it can be further discussed. |