| Summary: | Parents array Locations inconsistent with Directory metadata | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> |
| Component: | Node | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 5.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Mark Macdonald
This is caused by an inconsistency in the Parents array's Locations versus the Location field on an individual Directory. The latter has a trailing slash, but the former does not. // Metadata of /file/SomeToplevelFolder/foo.js?parts=meta: > Parents: [ > { Location: "/file/SomeToplevelFolder", Name: "SomeToplevelFolder" } ^ no slash > ] // Metadata of /file/SomeTopLevelFolder?parts=meta > { Location: "/file/SomeToplevelFolder/", Name: "SomeToplevelFolder", Directory: true } ^ slash The client expect these to be exactly the same, or else it can't tell that an ancestor of the file being edited was renamed. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |