3269 [BUGFIX] refactor reparse js file

[raftmsohani]

Summary of Changes

Pull request closes #3269

How to Test

1. Open http://localhost:3000/ and sign in.
2. Proceed to admin -> datafile
3. You will need more than 500 datafiles to test the functionality. If you are testing this locally, you can create a loop using backend-exec-seed-db (you will need to change the script to use multiple STTs in a loop), otherwise test this in dev env
4. If reparse command is not used, then form will not be submitted. Otherwise if 'reparse' command is chosen, then modal will show the number of files to be reparsed.

Deliverables

More details on how deliverables herein are assessed included here.

Deliverable 1: Accepted Features

Checklist of ACs:

• [insert ACs here]
• lfrohlich and/or adpennington confirmed that ACs are met.

Deliverable 2: Tested Code

• Are all areas of code introduced in this PR meaningfully tested?
  • If this PR introduces backend code changes, are they meaningfully tested?
  • If this PR introduces frontend code changes, are they meaningfully tested?
• Are code coverage minimums met?
  • Frontend coverage: [insert coverage %] (see CodeCov Report comment in PR)
  • Backend coverage: [insert coverage %] (see CodeCov Report comment in PR)

Deliverable 3: Properly Styled Code

• Are backend code style checks passing on CircleCI?
• Are frontend code style checks passing on CircleCI?
• Are code maintainability principles being followed?

Deliverable 4: Accessible

• Does this PR complete the epic?
• Are links included to any other gov-approved PRs associated with epic?
• Does PR include documentation for Raft's a11y review?
• Did automated and manual testing with iamjolly and ttran-hub using Accessibility Insights reveal any errors introduced in this PR?

Deliverable 5: Deployed

• Was the code successfully deployed via automated CircleCI process to development on Cloud.gov?

Deliverable 6: Documented

• Does this PR provide background for why coding decisions were made?
• If this PR introduces backend code, is that code easy to understand and sufficiently documented, both inline and overall?
• If this PR introduces frontend code, is that code easy to understand and sufficiently documented, both inline and overall?
• If this PR introduces dependencies, are their licenses documented?
• Can reviewer explain and take ownership of these elements presented in this code review?

Deliverable 7: Secure

• Does the OWASP Scan pass on CircleCI?
• Do manual code review and manual testing detect any new security issues?
• If new issues detected, is investigation and/or remediation plan documented?

Deliverable 8: User Research

Research product(s) clearly articulate(s):

• the purpose of the research
• methods used to conduct the research
• who participated in the research
• what was tested and how
• impact of research on TDP
• (if applicable) final design mockups produced for TDP development

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.48%. Comparing base (dd5ea65) to head (c2d142a).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #3280   +/-   ##
========================================
  Coverage    91.48%   91.48%           
========================================
  Files          297      297           
  Lines         8433     8433           
  Branches       611      611           
========================================
  Hits          7715     7715           
  Misses         605      605           
  Partials       113      113           

Flag	Coverage Δ
dev-backend	91.34% <ø> (ø)
dev-frontend	92.51% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd5ea65...c2d142a. Read the comment docs.

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[elipe17]

This works as advertised. But is there not a way for us to select the element containing the selected number of files instead of looping through children manually? Could we do something more like: document.querySelector("span.all");? I tried in the dev tools to see if it works and it returns the right element. We would just need to split on the space character to extract the number. We would also need to check that the element isn't hidden. If it was, then we just grab the other span.

[elipe17]

Forgot to include the screenshot:

[elipe17]

Left a suggestion. Let me know what you think.

[elipe17]

LGTM!

[andrew-jameson]

LGTM

[ADPennington]

lgtm! 🚀