Skip to content

fix: mt-field-error supporting meta properties#1137

Open
Arnold Stoba (arnoldstoba) wants to merge 3 commits intomainfrom
fix/mt-error-supporting-meta-properties
Open

fix: mt-field-error supporting meta properties#1137
Arnold Stoba (arnoldstoba) wants to merge 3 commits intomainfrom
fix/mt-error-supporting-meta-properties

Conversation

@arnoldstoba
Copy link
Copy Markdown

What?

Fixes #906 to support both parameters and meta.parameters

Why?

According to the ticket error responses are often in props.error.meta.parameters, and supporting that out of the box seems valid

How?

  • Added support for both meta.parameters as well as parameters as possible sources in the mt-field-error component, which are then passed into the translation

Testing?

  • Adjusted unit test to test the behavior of the different error values

Screenshots (optional)

Anything Else?

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

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

Project Deployment Actions Updated (UTC)
meteor-component-library Ready Ready Preview, Comment Apr 23, 2026 4:16pm

Request Review

@arnoldstoba Arnold Stoba (arnoldstoba) force-pushed the fix/mt-error-supporting-meta-properties branch from 4f0548e to f696197 Compare April 23, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Meteor fields don't resolve error snippets correctly.

1 participant