Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Card Archiving Functionality with Documentation Updates #724

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

robsonvnt
Copy link
Contributor

Description:

This pull request introduces the functionality to archive cards within the system, utilizing the existing delete confirmation popup to minimize code changes. The feature has been implemented across both the backend and frontend and includes the necessary database updates.

Main Changes:

  • Implementation of the option to archive cards.
  • Creation of a 'status' column in the cards table to manage the archiving state, along with corresponding database migrations.
  • Reuse of the delete confirmation popup for the archiving action.
  • Improvements to the development environment documentation to assist new contributors.

Observations:

  • Currently, I have implemented only the archiving functionality. A method to unarchive cards still needs to be developed.
  • I am seeking suggestions to improve the implementation, considering my limited experience with JavaScript, React, Redux, and Redux-Saga.
  • I was unable to find an "alternate outline" icon in Semantic-UI that was suitable for this functionality. Any recommendations for icons are welcome.

Request for Feedback:

Given my limited experience with these technologies, I am open to receiving feedback on the coding practices adopted, as well as suggestions for improvements or corrections that could enhance the quality and maintainability of the code.

Next Steps:

  • Development of the functionality to unarchive cards.
  • Continuous improvement of the documentation.

…responding 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.
@meltyshev
Copy link
Member

Hi! Thanks for working on this 🙏

We've already started working on archiving in v2, but we can't move it here since the code is already very different. I'll try to check everything out this week.

@robsonvnt
Copy link
Contributor Author

Is V2 in another repository?

@meltyshev
Copy link
Member

Is V2 in another repository?

Nope, it will be the same repo when we finish.

@meltyshev
Copy link
Member

Hi! I apologize for not replying here for a while.

I've tested a bit and have a few notes:

  • Wouldn't there be a problem with card positioning with this approach? Since the cards are still stored in the same list (just marked as archived). Or probably they should be removed from repositioning process.
  • There may also be a problem that all cards are always being loaded with a board, which can cause loading problems if there are a lot of archived cards.

Should we wait until the unarchiving is done?

BTW, thanks for improving the development environment documentation :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants