Project

Profile

Help

Task #7776

Document to not use setting in the model fields

Added by ipanova@redhat.com 12 months ago. Updated 5 months 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

Associated revisions

Revision f5d1a3e6 View on GitHub
Added by ipanova@redhat.com 5 months ago

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

closes #7776

History

#1 Updated by bmbouter 5 months ago

  • Quarter set to Q2-2021
  • Tags Easy Fix added

#2 Updated by ipanova@redhat.com 5 months ago

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

#3 Updated by pulpbot 5 months ago

  • Status changed from ASSIGNED to POST

#4 Updated by ipanova@redhat.com 5 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#5 Updated by dalley 5 months ago

  • Sprint/Milestone set to 3.13.0

#6 Updated by pulpbot 5 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF