feat: vai error show

[cuzz-venus]

Jira ticket(s)

VPD-1256

Changes

• remove description

before:

after:

[changeset-bot]

🦋 Changeset detected

Latest commit: 290bf4b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@venusprotocol/evm	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dapp-preview	Ready	Preview	May 31, 2026 3:55pm
dapp-testnet	Ready	Preview	May 31, 2026 3:55pm
venus.io	Ready	Preview	May 31, 2026 3:55pm

[greptile-apps]

Greptile Summary

This PR refactors error handling in the VAI Borrow and Repay forms by moving translated error messages directly into the Zod schema refinements (via t() in useForm), and removing the separate NoticeError components and errorMessage useMemo blocks that previously translated raw ErrorCode enum values.

• Borrow & Repay useForm: ErrorCode enum entries are replaced with inline t() calls inside Zod .refine() messages; t (and vai where vai.symbol is used) are added to the useMemo dependency array so the schema rebuilds on locale change.
• Borrow & Repay page components: The errorMessage useMemo and <NoticeError> blocks are removed; errors are now surfaced inline below the amount input via RhfTokenTextField's existing fieldState.error.message display.
• Repay page: The isRepayingFullLoan warning guard is updated from !errorMessage to !formState.errors.amountTokens, preserving the original intent.

Confidence Score: 5/5

Safe to merge — the change removes redundant UI components and consolidates error display into the existing inline mechanism without altering any business logic.

The translated strings are now computed at schema-build time and correctly keyed on t and vai in the dependency arrays, so locale changes trigger schema rebuilds as expected. RhfTokenTextField was already rendering fieldState.error.message as red text inline before this PR, so removing the external NoticeError components does not regress any error visibility.

No files require special attention.

Important Files Changed

Filename	Overview
apps/evm/src/pages/Vai/Borrow/useForm/index.ts	Moves error translation into the Zod schema refinements using t(), adds t to the useMemo dependency array, removes now-unused ErrorCode enum entries
apps/evm/src/pages/Vai/Borrow/index.tsx	Removes the errorMessage useMemo and the NoticeError component; error display now handled inline by RhfTokenTextField's built-in fieldState.error.message rendering
apps/evm/src/pages/Vai/Repay/useForm/index.ts	Same pattern as Borrow — translates error messages at schema-build time, removes ErrorCode enum, adds t and vai to the dependency array
apps/evm/src/pages/Vai/Repay/index.tsx	Removes errorMessage useMemo and NoticeError; fixes the full-repayment warning guard to check formState.errors.amountTokens directly instead of the now-removed errorMessage
.changeset/fast-drinks-stop.md	Patch changeset entry for the VAI error message refactor

_{Reviews (3): Last reviewed commit: "feat: remove raw translate key" | Re-trigger Greptile}

[github-actions]

Coverage Report for ./apps/evm

Status	Category	Percentage	Covered / Total
🔵	Lines	81.31%	45799 / 56324
🔵	Statements	81.31%	45799 / 56324
🔵	Functions	62.21%	647 / 1040
🔵	Branches	72.26%	5155 / 7133

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
apps/evm/src/pages/Vai/Borrow/index.tsx	95.08%	84.09%	100%	95.08%	62, 85-86, 101, 111, 199-203, 220-221
apps/evm/src/pages/Vai/Borrow/useForm/index.ts	99%	95%	100%	99%	1
apps/evm/src/pages/Vai/Repay/index.tsx	94.52%	52.94%	100%	94.52%	60-61, 127-131, 154-155, 163-165
apps/evm/src/pages/Vai/Repay/useForm/index.ts	97.46%	77.77%	100%	97.46%	1, 38

Generated in workflow #13531 for commit 290bf4b by the Vitest Coverage Report Action

[cuzz-venus]

@greptile review again

[therealemjy]

I'd recommend taking a different approach.

This form is behaving differently in the sense that we use a custom UI to show errors. The designs were made quite a while ago and so I think we'd be better off staying consistent with the newest form.

So the approach I propose is to update the useForm hook of this component so that the error that's set on the field isn't an error code but rather the full error message. This means the RhfTokenTextField component won't need to be updated and will natively display the human-friendly error message.

[cuzz-venus]

Makes sense, fully agree — going with the consistent form pattern is cleaner. I've updated the useForm hooks for both Repay and Borrow to set the translated message directly on the field, and removed the custom NoticeError UI in the parent components. RhfTokenTextField is back to untouched and now natively shows the human-friendly message.

One small note — I kept ErrorCode.REQUIRES_RISK_ACKNOWLEDGEMENT as-is on the acknowledgeRisk field since it's only used as an internal state marker (never displayed to the user, and there's no matching i18n key for it). Let me know if you'd prefer to clean that up too. 😄

[cuzz-venus]

[cuzz-venus]

@greptile review again