[BUG] Governance Action Proposal Submission Metadata Anchor Validation

[kneerose]

Context & versions

• This issue is related to #1180
• The proposal submission metadata URL field allows users to enter URLs exceeding the expected character limit (greater than 128 bytes) and does not display any error message if the URL is invalid.
• For reference look into the dRep Registration metadata anchor validation

Steps to reproduce

• Navigate to created proposal details.
• Submit it as a governance action.
• In the metadata anchor field, enter a URL that
  • Exceeds 128 bytes
  • Is an Invalid URL.
• Observe that the submit button remains enabled and no error message is displayed.

Actual behaviour

• No error message is shown, and the submit button is enabled despite the URL exceeding the character limit and being invalid.

Expected behaviour

• An appropriate error message should be displayed to clearly inform the user when:
  • The URL exceeds 128 bytes.
  • The URL is invalid.
• The submit button should be disabled until a valid URL is entered.

Report Reference

• https://cardanoapi.github.io/govtool-test-reports/govtool-frontend/63/#behaviors/1c853b5eba2ae76bed30628cc87b9764/10ceebd7e95698be/

[teske00]

@kneerose It is deployed on dev, it can be tested

[kneerose]

I have reviewed your changes, but it seems you missed adding test IDs for the new components. Please ensure that you include proper test IDs for any new components in the future.

[vpaunovic]

@kneerose It can be tested on dev with new version of pdf now.

CC: @bosko-m

[kneerose]

@vpaunovic

The "Required" message is always visible. Is it intended to be always visible? Currently, the test ID used for "Required" is the same as that for "Invalid URL" and "URL must be less than 128 bytes." This will conflict with our test. If the "Required" message is intended always to be shown, please use a different test ID for each message.

[vpaunovic]

@kneerose It is required. It is helper text, not an error. The error is red color and red border around input.. so.. i will put different testid string in case if it is error or just helper text.And we will put it in new pdf package version! 😀

cc: @teske00

[vpaunovic]

@kneerose It is fixed and it will be available in new pdf package version and when it is deployed on dev. It will have required-url-input-text data-testid when there is no error and just Required text as helperText.

CC: @teske00

[kneerose]

@vpaunovic I see the changes on the dev environment but not yet on the test environment . The ticket will be closed once the changes are available in the test environment. CC: @bosko-m

[bosko-m]

Please dont close it after it passes the testing on test environment @kneerose . Intersect should give in this case final sign off after testing it on staging.

[kneerose]

I've reviewed the changes on the test environment. This issue can be closed now.
CC: @bosko-m

[bosko-m]

Closing as per the comment above.