DAST Profiles forms - Improve code reusability
Problem to solve
Both the DAST Site profile form and the DAST Scanner profile form share similar functionalities:
- Rename the
dast_site_profiles_form
dir todast_site_profiles
. - They both trigger a GraphQL mutation for either creating or updating a profile.
- They have similar (not to say identical) computed properties for keeping track of the form's state.
- They accept similar props.
- They deal with errors similarly.
- They both handle submission in a similar way.
- ...
Let's figure out a way to normalize and share as much code as possible between those two components to reduce duplication and improve maintainability.
- Related discussion: !40963 (comment 405944792)
Edited by Paul Gascou-Vaillancourt