-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[NoQA] change webpack config and rename .web files to .website files #32548
[NoQA] change webpack config and rename .web files to .website files #32548
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
4a73cfe
to
820fb32
Compare
I have read the CLA Document and I hereby sign the CLA |
@marcochavezf Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
recheck |
🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
|
@mountiny iOS has failed 🤔 |
Looks like the iOS build was cancelled without specific reason. Maybe another build will solve it. cc @blazejkustra @mountiny |
that probs does not matter here |
Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build seem to be working fine @marcochavezf all yours!
@SzymczakJ Fill out |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also LGTM
@marcochavezf @mountiny What's next, do we need a C+ for this one or proceed with a merge? 😅 |
Reviewer Checklist
Screenshots/VideosConfirmed web and desktop are building correctly, otherwise n/a Android: NativeAndroid: mWeb ChromeiOS: NativeiOS: mWeb SafariMacOS: Chrome / SafariMacOS: Desktop |
Will merge this one then |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.10-0 🚀
|
🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.10-0 🚀
|
🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.10-1 🚀
|
🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.10-1 🚀
|
@@ -47,5 +47,5 @@ | |||
} | |||
}, | |||
"exclude": ["**/node_modules/*", "**/dist/*", ".github/actions/**/index.js", "**/docs/*"], | |||
"include": ["src", "desktop", "web", "docs", "assets", "config", "tests", "jest", "__mocks__", ".github/**/*", ".storybook/**/*"] | |||
"include": ["src", "desktop", "web", "website", "docs", "assets", "config", "tests", "jest", "__mocks__", ".github/**/*", ".storybook/**/*"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This config change caused #40152.
I don't think so that we would had prevented this though.
Details
Webpack doesn't include .desktop.tsx files in bundle when running desktop app and desktop app wouldn't work if we wanted to write some desktop specific code. This PR fixes it and unblocks this task , that has components that have such .desktop.tsx files. I've also noticed that some of our web specific files have .web suffix and renamed then to have .website suffix for better standarization.
Fixed Issues
$ #24990 related to
PROPOSAL: N/A
Tests
Offline tests
N/A
QA Steps
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Android: Native
android.mov
Android: mWeb Chrome
androidweb.mov
iOS: Native
ios.mov
iOS: mWeb Safari
iosmweb.mov
MacOS: Chrome / Safari
websitesmal.mov
MacOS: Desktop
desktop.mov