-
Notifications
You must be signed in to change notification settings - Fork 3
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
#225 fx-Remove ratings legacy feature #594
Open
Bananayosostene
wants to merge
1
commit into
develop
Choose a base branch
from
Remove-ratings-legacy-feature-#225
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bananayosostene
requested review from
Salim-54,
JacquelineTuyisenge,
Dawaic6,
janet-barbie and
shebz2023
October 18, 2024 12:48
Bananayosostene
force-pushed
the
Remove-ratings-legacy-feature-#225
branch
from
October 19, 2024 09:14
bd583b9
to
87e12a2
Compare
Tuyisenge2
approved these changes
Oct 21, 2024
Dawaic6
approved these changes
Oct 21, 2024
shema-surge
requested changes
Oct 21, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Remove bodyQuality, bodyQuantity and bodyProfessional
- "generalRemarks" is no longer needed, keep "feedbacks" only
Bananayosostene
force-pushed
the
Remove-ratings-legacy-feature-#225
branch
from
October 22, 2024 14:13
87e12a2
to
5939e87
Compare
JacquelineTuyisenge
approved these changes
Oct 22, 2024
shema-surge
approved these changes
Oct 22, 2024
Bananayosostene
force-pushed
the
Remove-ratings-legacy-feature-#225
branch
from
October 23, 2024 13:26
5939e87
to
e361854
Compare
Bananayosostene
force-pushed
the
Remove-ratings-legacy-feature-#225
branch
from
October 24, 2024 09:58
e361854
to
b909a34
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
This PR addresses the removal of legacy features on the frontend, specifically the non-implemented fields qualityRemark, quantityRemark, and professionalismRemark, which were redundant and not utilized. The feedback and rating functionality remain as the primary feature for user feedback.
Description of tasks that were expected to be completed
Confirmed that the legacy fields were not implemented on the frontend.
Verified that no changes or updates were required in terms of visual or functional implementation related to these fields.
Cleaned up any mentions or potential references to the fields if found.
How has this been tested?
Manual review: Ensured that no unintended front-end changes related to qualityRemark, quantityRemark, and professionalismRemark exist.
Browser testing: Verified that the existing feedback and ratings features work as expected without any issues.
Number of Commits
1 commit for the changes. Squashed if necessary.
Screenshots (If appropriate)
(Optional)
Please check this Checklist before you submit your PR:
My code follows the style guidelines of this project.
I have performed a self-review of my code.
My code generates no warnings.
My test coverage meets the set test coverage threshold.
There are no vulnerabilities.
There are no conflicts with the base branch.