Patron Notice form Validation fires too often, causing unnecessary requests.

In PatronNoticeAboutSection - the validation function validateName is re-intialized/remade every render causing its logic to be re-executed. The function likely needs to be wrapped in a render-stable hook (useRef, useCallback) rather than declared directly.

Opening the Network tab in Chrome devtools, the request to pull templates for validating names happens with every keystroke in the editor for the template’s message. The request logic lives in the validation function of the ‘name’ field.

We originally thought that stripes-template-editor was to blame, but this is resolvable at the form level. It should not validate the uniqueness of ‘name’ when the ‘name’ field itself did not change.