Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add new salesforce site scoped module for default language (@W-12984619) #180

Closed
wants to merge 1 commit into from

Conversation

Fatema-Saifee
Copy link

Adding the site/defaultLanguage scoped module.

Awaits the corresponding PRs to lwc repos.

✅ Request:

✅ Spec: https://salesforce.quip.com/1v2yASgA0Lyf

@salesforce-cla
Copy link

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Fatema Saifee <f***@f***.i***.s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce Inc. Contributor License Agreement and this Pull Request will be revalidated.

@nolanlawson
Copy link
Contributor

Thanks for the PR! Could you please separate the stylistic changes from the functional changes?

@@ -139,3 +139,28 @@ describe('@salesforce/site/activeLanguages import', () => {
'Invalid import from @salesforce/site/activeLanguages'
);
});

describe('@salesforce/site/defaultLanguage import', () => {
Copy link
Author

Choose a reason for hiding this comment

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

@nolanlawson This is where the tests for defaultLanguage test are added!

@@ -20,6 +20,27 @@ const siteActiveLanguagesTemplate = babelTemplate(`
}
`);

const siteDefaultLanguagesTemplate = babelTemplate(`
Copy link
Author

Choose a reason for hiding this comment

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

@nolanlawson here are the changes for adding it to the import config!

@Fatema-Saifee
Copy link
Author

Thanks for the PR! Could you please separate the stylistic changes from the functional changes?

@nolanlawson I have commented on the 2 files where the functional changes are added. Rest all files have stylistic changes. I hope this is a bit clearer now!

@nolanlawson
Copy link
Contributor

Closing in favor of #181

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.

2 participants