Project

Profile

Help

Issue #3410

closed

Rename content field "path" to "relative_path"

Added by kersom almost 7 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Low
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
1. Low
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Sprint 33
Quarter:

Description

When reading content from a repository, the response is:

 {'next': None,
 'previous': None,
 'results': [{'_href': 'http://f27-p3:8000/api/v3/content/file/44f4dfa2-1b80-459c-960b-079c4dd6e48c/',
              'artifacts': {'2.iso': 'http://f27-p3:8000/api/v3/artifacts/cbce4558-59b9-4674-83d2-7f6dd2875b6e/'},
              'digest': '3a1b7f18cb8e51f381a9ceb32447fcdaa070d41bbf2d9bd12f5ea1731dfe0b0b',
              'notes': {},
              'path': '2.iso',
              'type': 'file'}]}

</code>

"path" should be renamed to "relative_path" to better denote its purpose.


Related issues

Related to File Support - Issue #3425: Path on content unit doesn't seem to do anythingCLOSED - DUPLICATEActions

Also available in: Atom PDF