Skip to content

Conversation

@olxmpe
Copy link
Contributor

@olxmpe olxmpe commented Jan 8, 2026

What does this PR do?

We use the same wording for generic form validation toasts across Upfluence ecosystem. Those translations are now each under a single translation key in OSS components to make forms more maintenable :

  • 'generic' success message
  • 'requirement' error when fields are misssing
  • 'format' error when format is invalid
  • 'format_and_requirement' when both

Related to: #6487

What are the observable changes?

Good PR checklist

  • Title makes sense
  • Is against the correct branch
  • Only addresses one issue
  • Properly assigned
  • Added/updated tests
  • Added/updated documentation
  • Migrated touched components to Glimmer Components
  • Properly labeled

@olxmpe olxmpe self-assigned this Jan 8, 2026
@linear
Copy link

linear bot commented Jan 8, 2026

@olxmpe olxmpe changed the title Centralize generic forms toast feedbacks Centralize generic forms toast feedbacks in OSS Components Jan 9, 2026
Copy link
Contributor

@Elodie-DeMatteis-Upf Elodie-DeMatteis-Upf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As this is an OSS PR, you should add some clear description in the PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants