Version: drop file field, use files instead #193
No reviewers
Labels
No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#193
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "version-drop-file"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #74.
This PR drops Extension.file field, and introduces a cached_property Extension.file
as a temporary replacement for existing code references to the dropped field.
VersionFiles is renamed to VersionFile to match naming conventions.
All reads and writes go only via VersionFile cross-table, still assuming a single File
record per Version.
No functional changes are expected, except for one unfortunate side-effect in
recording object deletion via LogEntry: Version deletion is recorded twice:
After this change is deployed, we can start implementing multiple file uploads per
Version to support multi-platform builds (generated with
--split-platforms
option).LGTM