#610 Bug-fix - Missing background-color added to style. #611

Merged
b24johka merged 2 commits from #610-reset-modal-background-not-displaying into team_1_week_3 2026-04-28 12:42:57 +00:00
Collaborator

Added missing background-color parameter to DangerModal.module.css.

image

Added missing background-color parameter to DangerModal.module.css. ![image](/attachments/ea73f53c-8f8e-4972-9f23-d1393a9b9aab)
Added missing background-color parameter to DangerModal.module.css.
Collaborator

Review on #611

What has been Done.

Reviewed code and tested so that DangerModal is displayed correctly.

Tested On Windows using Google Chrome.

  • App starts
  • Reset button works
  • The background color appears when pressing the reset button.

Inspected the following file "DangerModal.module.css.

  • The css does not follow our conventions and rules.
    • We are supposed to use hex codes for colors
    • all classes, id, attributes should be lowercase and separation should be made with a dash "-".
    • all declarations within the rule set should be ordered alphabetically.

What Needs to be done.

  • fix the code to follow our conventions and rules

Conclusion

The issue is technically fixed and can be merged but there are problems with the code standard based on our conventions stated here.

### Review on #611 ### What has been Done. Reviewed code and tested so that DangerModal is displayed correctly. ### Tested On Windows using Google Chrome. - App starts - Reset button works - The background color appears when pressing the reset button. ### Inspected the following file "DangerModal.module.css. - The css does not follow our conventions and rules. - We are supposed to use hex codes for colors - all classes, id, attributes should be lowercase and separation should be made with a dash "-". - all declarations within the rule set should be ordered alphabetically. - ### What Needs to be done. - fix the code to follow our conventions and rules ### Conclusion The issue is technically fixed and can be merged but there are problems with the code standard based on our conventions stated [here](https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/CSS-Coding-Convention).
Author
Collaborator

I'm going to dispute part of this review, as the ONLY thing that was changed, was literally the addition of one single line of code. Which means the second and third point are beyond the scope of this pull request. (Refactoring would be a separate issue entirely)

In regards to the first point, RGBA is generally recommended for transparencies, as they are easier to understand and adjust. Hex codes are best used for solid colors.

I'm going to dispute part of this review, as the ONLY thing that was changed, was literally the addition of one single line of code. Which means the second and third point are beyond the scope of this pull request. (Refactoring would be a separate issue entirely) In regards to the first point, RGBA is generally recommended for transparencies, as they are easier to understand and adjust. Hex codes are best used for solid colors.
Collaborator

@f21marfo wrote in #611 (comment):

I'm going to dispute part of this review, as the ONLY thing that was changed, was literally the addition of one single line of code. Which means the second and third point are beyond the scope of this pull request. (Refactoring would be a separate issue entirely)

In regards to the first point, RGBA is generally recommended for transparencies, as they are easier to understand and adjust. Hex codes are best used for solid colors.

Fair, i agree, which is why i have brough the issue with the conventions to the coordinator and leader since when checking for this i also looked at other css files and they all have these issues which is a problem since these should be hard "rules" we follow to make sure that our css files have a clear standard.

@f21marfo wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/611#issuecomment-6324: > I'm going to dispute part of this review, as the ONLY thing that was changed, was literally the addition of one single line of code. Which means the second and third point are beyond the scope of this pull request. (Refactoring would be a separate issue entirely) > > In regards to the first point, RGBA is generally recommended for transparencies, as they are easier to understand and adjust. Hex codes are best used for solid colors. Fair, i agree, which is why i have brough the issue with the conventions to the coordinator and leader since when checking for this i also looked at other css files and they **all** have these issues which is a problem since these should be hard "rules" we follow to make sure that our css files have a clear standard.
Collaborator

And for that second part about RGBA i believe that should be added to the wiki as well because as it stands in our wiki only hex codes should be used.

And for that second part about RGBA i believe that should be added to the wiki as well because as it stands in our wiki only hex codes should be used.
Collaborator

Ill change this to HEX and update the commit to go along with our convention.

Ill change this to HEX and update the commit to go along with our convention.
Collaborator

Review was sufficient, this will be merged right away.

Review was sufficient, this will be merged right away.
b24johka merged commit 854de7d3c7 into team_1_week_3 2026-04-28 12:42:57 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K!611
No description provided.