Allow users to reset DAST submit field
What does this MR do and why?
Problem: At the moment, it's not possible to reset DAST "submit field" for a site profile.
Why: When a user tries to empty the value of existing "submit field" from site profile, frontend do not send the field at all in the graphql mutation. This is because frontend do not send empty values in the mutation variables by default.
Solution: Make an exception for optional field
Screenshots or screen recordings
Please notice the submitField
is now being sent to the graphql request
before | after |
---|---|
How to set up and validate locally
- Create a site profile and save a
submit field
value - Now edit the profile and try to remove the value
- It should now be able to save an empty value
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.