Skip to content

Conversation

@MarkLi28
Copy link

@MarkLi28 MarkLi28 commented Sep 8, 2025

… of similar code

P1B: Starter Task: Refactoring PR

Use this pull request template to briefly answer the questions below in one to two sentences each.
Feel free to delete this text at the top after filling out the template.

You are not permitted to use generative AI services (e.g., ChatGPT) to compose the answers.
Any such use will be treated as a violation of academic integrity.

1. Issue

Please provide a link to the associated GitHub issue:

Link to the associated GitHub issue:
#267

Full path to the refactored file:
public/src/admin/dashboard.js

What do you think this file does?
(Your answer does not have to be 100% correct; give a reasonable, evidence‑based guess.)
I'm pretty sure dashboard.js fetches data from the serve and creates the graphics and stuff on the admin dashboard

What is the scope of your refactoring within that file?
(Name specific functions/blocks/regions touched.)
renderCustomRangeModal function

Which Qlty‑reported issue did you address?
(Name the rule/metric and include the BEFORE value; e.g., “Cognitive Complexity 18 in render()”.)
public/src/admin/dashboard.js
Found 19 lines of similar code in 2 locations

2. Refactoring

How did the specific issue you chose impact the codebase’s adaptability?
it improved adaptability by simplifying future updates and reducing complexity

What changes did you make to resolve the issue?
created a separate file for the shared function, then called that in both dashboard.js and dashboard-line-graph.js

How do your changes improve adaptability? Did you consider alternatives?
My changes improve adaptability by centralizing logic, so if a developer needs to change this function, they only need to do it in one place rather than two. I did not consider any alternatives.

3. Validation

How did you trigger the refactored code path from the UI?
I logged in using the admin account, went to the admin dashboard, and clicked the "custom time frame" button under the big graph.

Attach a screenshot of the logs and UI demonstrating the trigger.
(Run ./nodebb log; include the relevant UI view. Temporary logs should be removed before final commit.)
Screenshot 2025-09-08 at 6 27 14 PM

Attach a screenshot of qlty smells --no-snippets <full/path/to/file.js> showing fewer reported issues after the changes.
Screenshot 2025-09-08 at 7 03 12 PM

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.

1 participant