[patch] Fix custom labels handling in HalstackProvider - #2546
Merged
Merged
Conversation
PelayoFelgueroso
changed the title
Jialecl
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
(Check off all the items before submitting)
/libdirectory./websiteas needed.Description
Fix the handling of custom labels in HalstackProvider to ensure localized labels are correctly merged without mutating the default labels object.
Changes
Fix custom label parsing and merging in HalstackContext.
Prevent mutations to the default translated component labels.
Update the localization examples to use the correct placeholder prop.
Impact
This ensures custom component labels provided through HalstackProvider are correctly applied while preserving the default labels.