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

[Cross-Check]: Deprecate "Bad Comment" Functionality in Cross-Check Table #2422

Open
7 tasks
valerydluski opened this issue Feb 3, 2024 · 0 comments
Open
7 tasks
Labels
good first issue Good for newcomers

Comments

@valerydluski
Copy link
Contributor

Description

The functionality labeled "bad comment" found on the Cross-Check Table page at {host}/course/admin/cross-check-table?course={course-alias} is scheduled for deprecation. Additionally, the backend code supporting this feature, located at getBadComment.ts, needs to be removed. This change is aimed at streamlining the cross-check process and ensuring the relevance and efficiency of the administrative tools.

Objectives

  • Deprecation of Frontend Feature: Removing the "bad comment" functionality from the Cross-Check Table page to simplify the user interface.
  • Backend Code Removal: Deleting the associated backend code to maintain codebase cleanliness and relevance.

Tasks

  1. Frontend Feature Deprecation:

    • Identify all instances and references of the "bad comment" functionality in the frontend.
    • Remove the UI elements related to this feature from the Cross-Check Table page.
  2. Backend Code Removal:

    • Locate the getBadComment.ts file in the repository.
    • Delete the file and any related code snippets that are exclusively used by this feature.
    • Ensure that the removal does not affect other functionalities.
  3. Quality Assurance:

    • Conduct thorough testing to confirm that the deprecation does not introduce any bugs or issues.
    • Validate that the removal of the backend code does not impact other areas of the application.

Expected Outcome

The successful completion of these tasks will result in a cleaner, more focused user interface for the Cross-Check Table page, and a streamlined codebase by removing obsolete code. This will enhance the overall efficiency and usability of the application for administrators.

Additional Notes

It is important to coordinate with both the frontend and backend teams to ensure a smooth transition. Any potential dependencies or integrations with other features should be carefully reviewed and addressed to avoid unintended side effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
No open projects
Status: In Progress
Development

No branches or pull requests

2 participants