Trailing slash in path of LL object causes unintended beavior #70

New issue

Closed

opened 2026-07-31 12:27:18 +00:00 by scossu · 1 comment

scossu commented

2026-07-31 12:27:18 +00:00

Owner

If a slash is appended at the end of a path (supposedly a container / folder type), trees created from that path behave incorrectly:

They create a double hierarchy, once inside the parent, once at the same parent level.
If the path with the trailing slash is inside a parent, it is not included in the parent's tree.

Normalizing the paths by removing all trailing slashes removes the problem, and is the best option. Some Unix tools give special meaning to trailing slashes: that's good for sysadmins, but confusing for catalogers.

If a slash is appended at the end of a path (supposedly a container / folder type), trees created from that path behave incorrectly: 1. They create a double hierarchy, once inside the parent, once at the same parent level. 2. If the path with the trailing slash is inside a parent, it is not included in the parent's tree. Normalizing the paths by removing all trailing slashes removes the problem, and is the best option. Some Unix tools give special meaning to trailing slashes: that's good for sysadmins, but confusing for catalogers.

scossu added this to the v1.0.0 milestone

2026-07-31 12:27:18 +00:00

scossu added the

area/submission

bug

high

labels

2026-07-31 12:27:18 +00:00

scossu referenced this issue from a pull request that will close it,

2026-07-31 15:19:21 +00:00

Remove trailing slashes from LL paths. #71

scossu closed this issue