Added card archiving functionality and created status column with corresponding migrations
- Implemented the option to archive cards in the system, with support in both backend and frontend. - Created 'status' column in the cards table to manage archiving status. - Developed necessary database migrations for the new column. - Reused the delete confirmation popup to confirm archiving, minimizing code changes. - Modifications made to backend handlers and frontend UI to support the archiving functionality.pull/724/head
parent
03825c3bed
commit
60c514b63f
@ -0,0 +1,3 @@
|
||||
import ConfirmStep from './ConfirmStep';
|
||||
|
||||
export default ConfirmStep;
|
||||
@ -1,3 +0,0 @@
|
||||
import DeleteStep from './DeleteStep';
|
||||
|
||||
export default DeleteStep;
|
||||
@ -0,0 +1,11 @@
|
||||
exports.up = async (knex) => {
|
||||
await knex.schema.table('card', (table) => {
|
||||
table.enum('status', ['active', 'archived']).defaultTo('active').notNullable();
|
||||
});
|
||||
};
|
||||
|
||||
exports.down = async (knex) => {
|
||||
await knex.schema.table('card', (table) => {
|
||||
table.dropColumn('status');
|
||||
});
|
||||
};
|
||||
Loading…
Reference in New Issue