Project

Profile

Help

Issue #5009

closed

HTML in our json api schema

Added by daviddavis over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 59
Quarter:

Description

I noticed some strange descriptions for actions in our api schema when viewing it as json. I'm hitting the /pulp/api/v3/docs/api.json endpoint and seeing:

<!-- User-facing documentation, rendered as html-->\nFileRemote represents an external source of <a href=\"#operation/content_file_files_list\">File\nContent</a>.  The target url of a FileRemote must contain a file manifest, which contains the\nmetadata for all files at the source.

I wonder if we should avoid including html in fields as our api schema since it can be rendered in many different forms (e.g. json).

I see a few downsides to having HTML in our api schema:

1. This forces me and pulp users like me who prefer to less our api json docs to now use the generated html docs instead. I prefer to stick to the command line whenever possible.
2. Tools may eventually read/display these descriptions. I am thinking of potential tools like a pulp cli, tools that generate stuff like bash scripts or ansible roles, etc.
3. Other tools that can generate HTML like a Pulp web UI may not be able to properly generate this html. Stuff like links may not work properly.

Also available in: Atom PDF