#507-breakout-danger-modal #520

Closed
e24aleli wants to merge 0 commits from #507-breakout-danger-modal into team_1_week_3
Collaborator

Made a new directory called DangerModal that holds the button logic and css for both the modal and the button.

Also cleaned up remainders of the previous reset button that was in dashboard.js

Made a new directory called DangerModal that holds the button logic and css for both the modal and the button. Also cleaned up remainders of the previous reset button that was in dashboard.js
f21marfo left a comment
Collaborator

Review on #507

Whats done

Tested on Windows 11 25H2 using Edge

  • [Focus on checking features that the issue intended to solve/implement]
  • App starts [IF the app starts]
    • App loads and runs as expected.
    • Added widgets and clicked the "reset" button, appears to function as expected.

Inspected following files

  • Dashboard.module.css
    • General code quality
      • Code changes to not appear relevant to the Issue.
  • index.js
    • General code quality
      • Single code line conforms identically to the rest of the code in this file, on all points.
  • Dashboard.js
    • Indentation/code styling
      • Mostly good, use of DangerModal component has indendtation issue at line 204.
    • Naming convention
      • Checks out.
    • General code quality
      • Use of DangerModal could be cleaner with the use of a self closing tag instead of .
  • DangerModal.module.css
    • No comment really, it's a cut-and-paste of existing code in Dashboard.module.css.
  • DangerModal.js
    • Indentation/code styling
      • Looks Ok.
    • Naming convention [Including filename ]
      • Looks Ok.
    • Comments
      • Looks Ok.

What needs to be done

[Here you should write the things that needs to be fixed.]

  • Dashboard.module.css
    • These changes are not relevant to the issue and need to be omitted.

Conclusion

  • Code mostly looks good if the intent is for the entire modal is meant to be broken out and not just the button. Commits not related to the issue need to be omitted before merge.
# Review on #507 ## Whats done ### Tested on Windows 11 25H2 using Edge + [Focus on checking features that the issue intended to solve/implement] + App starts [IF the app starts] + App loads and runs as expected. + Added widgets and clicked the "reset" button, appears to function as expected. ### Inspected following files + Dashboard.module.css + General code quality + Code changes to not appear relevant to the Issue. + index.js + General code quality + Single code line conforms identically to the rest of the code in this file, on all points. + Dashboard.js + Indentation/code styling + Mostly good, use of DangerModal component has indendtation issue at line 204. + Naming convention + Checks out. + General code quality + Use of DangerModal could be cleaner with the use of a self closing tag instead of </DangerModal>. + DangerModal.module.css + No comment really, it's a cut-and-paste of existing code in Dashboard.module.css. + DangerModal.js + Indentation/code styling + Looks Ok. + Naming convention [Including filename ] + Looks Ok. + Comments + Looks Ok. ## What needs to be done [Here you should write the things that needs to be fixed.] + Dashboard.module.css + These changes are not relevant to the issue and need to be omitted. ## Conclusion + Code mostly looks good if the intent is for the entire modal is meant to be broken out and not just the button. Commits not related to the issue need to be omitted before merge.
Collaborator

I dont think .toolbar and .toolbarcontainer in the CSS file is related to the component, it should probably be removed

I dont think .toolbar and .toolbarcontainer in the CSS file is related to the component, it should probably be removed
Author
Collaborator

The toolbar classes are for the button i was thinking of importing the css file that dashboard uses but thought it would cause problems maybe i should just rename them?

The toolbar classes are for the button i was thinking of importing the css file that dashboard uses but thought it would cause problems maybe i should just rename them?
Collaborator

as long as the danger button is inside .toolbar and .toolbarcontainer classes in the code they should just go under dashboard.module.css? I will try this out and see if this is the case.

as long as the danger button is inside .toolbar and .toolbarcontainer classes in the code they should just go under dashboard.module.css? I will try this out and see if this is the case.
Collaborator

I tried the mention above and it works good, break it out of the CSS class please since it belongs to dashboard.module.css

I tried the mention above and it works good, break it out of the CSS class please since it belongs to dashboard.module.css
b24johka left a comment
Collaborator

Remove toolbar related items

Remove toolbar related items
Author
Collaborator

I removed the CSS inside of DangerModal file, seems to work.

I removed the CSS inside of DangerModal file, seems to work.
Collaborator

This has been manually merged as the review is sufficient for this PR. Good job!

This has been manually merged as the review is sufficient for this PR. Good job!
Collaborator

On a second notice i have seen that the dark overlay from the modal is not active when modal pops up. This will be a seperate issue and PR.

On a second notice i have seen that the dark overlay from the modal is not active when modal pops up. This will be a seperate issue and PR.
b24johka closed this pull request 2026-04-28 08:13:54 +00:00

Pull request closed

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!520
No description provided.