Skip to content
This repository has been archived by the owner on Jul 24, 2020. It is now read-only.

Upgrade permanent_record or roll our own soft-deletion #1639

Open
esoterik opened this issue Oct 2, 2016 · 0 comments
Open

Upgrade permanent_record or roll our own soft-deletion #1639

esoterik opened this issue Oct 2, 2016 · 0 comments
Labels
diff: 5 pri: 3 type: enhancement
Milestone
Spring 2017

Comments

@esoterik
Copy link
Collaborator

esoterik commented Oct 2, 2016 •
edited
Loading

#1638 identified an issue with the most recent permanent_record version that broke EquipmentModel#destroy. The issue was resolved by downgrading the gem, which isn't ideal but a quick fix was necessary.

We should either figure out how to upgrade permanent_record without breaking deactivation, or we should roll our own soft-deletion to avoid issues like this in the future.
@esoterik esoterik added this to the 6.3.0 milestone Oct 2, 2016
@esoterik esoterik changed the title Remove permanent_record, write our own soft-deletion Upgrade permanent_record or roll our own soft-deletion Oct 2, 2016
@esoterik esoterik modified the milestones: 6.4.0, 6.3.0 Oct 9, 2016
@esoterik esoterik modified the milestones: 6.3.0, Spring 2017 Jan 21, 2017
@orenyk orenyk mentioned this issue Jun 21, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
diff: 5 pri: 3 type: enhancement
Projects
None yet
Milestone
Spring 2017
Development

No branches or pull requests
1 participant
@esoterik