Task #2300: Add serializer for the task models. - Pulp

Actions

Send by e-mail Copy link

Task #2300

closed

Add serializer for the task models.

Added by jortel@redhat.com about 8 years ago. Updated about 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

bizhang

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Sprint:

Sprint 9

Quarter:

Description

Write a serializer for each model in task.py.

Related issues

Actions

Copy link

Updated by jortel@redhat.com about 8 years ago

Copied from Task #2299: Add serializer for the content models. added

Actions

Copy link

Updated by jortel@redhat.com about 8 years ago

Copied to Task #2301: Add serializer for the catalog models. added

Actions

Copy link

Updated by amacdona@redhat.com about 8 years ago

Blocks Task #2312: Add a Task ViewSet added

Actions

Copy link

Updated by amacdona@redhat.com about 8 years ago

Groomed changed from No to Yes

Actions

Copy link

Updated by semyers about 8 years ago

This task cannot be started until the documentation written in #1873 is merged to 3.0-dev.

Actions

Copy link

Updated by mhrivnak about 8 years ago

Sprint/Milestone set to 27

Actions

Copy link

Updated by semyers about 8 years ago

This task should be considered complete when all serializers for a given models module are defined in a corresponding serializers module.

The serializers defined should expose fields "native" (defined directly on a model or in its superclasses) to the model being represented, including Generic Key/Value types (Config/Notes/Scratchpad). Relations to other models should be included where possible, but the available serializer base classes and fields may be insufficient, so only the "native" fields should be required.

This task is among several similar tasks to stub out serializers for our existing models. Please spread the work around so we gain more team-wide knowledge around these serializers. If you have any questions, ask me. Common issues and their resolutions will be added to the pulp 3.0 rest-api development guide.

Actions

Copy link