fix: export messages object in translations/index.js #1444
Closed
Conversation
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
|
No longer required as translations are now automatic |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This Pull Request addresses issue #1429.
The translations/index.js file did not exist previously. This PR creates the file and defines a messages object containing localized welcome and goodbye messages in English and French. The messages object is exported as the default export, enabling other parts of the project to import and use these messages properly.
✅ Changes Made:
Created translations/index.js
Added and exported the messages object
🧪 Testing:
Verified the file exports without syntax errors
📌 Notes:
This helps fix missing exports and supports localization features in the project.