Project

Profile

Help

Task #7776

closed

Document to not use setting in the model fields

Added by ipanova@redhat.com almost 2 years ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Easy Fix
Sprint:
Sprint 97
Quarter:
Q2-2021

Description

Problem

Settings should not be used in the models fields

Proposal

Add to the plugin writers docs to not use settings in the models fields but rather 'hardcode' those values, since settings can change which will lead to a data migration

Actions #1

Updated by bmbouter over 1 year ago

  • Quarter set to Q2-2021
  • Tags Easy Fix added
Actions #2

Updated by ipanova@redhat.com over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com
  • Sprint set to Sprint 97
Actions #3

Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST

Added by ipanova@redhat.com over 1 year ago

Revision f5d1a3e6

Updated plugin writers' guide to not use settings directly in the model fields.

closes #7776

Actions #4

Updated by ipanova@redhat.com over 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #5

Updated by dalley over 1 year ago

  • Sprint/Milestone set to 3.13.0
Actions #6

Updated by pulpbot over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF