Move DAST profile summaries into separate components
What does this MR do?
This MR tries to refactor DAST Profile Summary by moving it to a new & dedicated component
- summary for Scanner Profiles is moved to
DastScannerProfileSummary
- summary for Site Profiles is moved to
DastSiteProfileSummary
This makes it
- easy to unit test
- easy to update / maintain
- and doesn't bloat
OnDemandScansForm
component
Screenshots (strongly suggested)
No visual changes
Does this MR meet the acceptance criteria?
Conformity
- [-] I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
- It doesn't require a changelog entry since there are no user facing changes
- [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
-
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) - [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. - [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Closes #330708 (closed)
Edited by Dheeraj Joshi