-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[No QA] Cleanup implementation of HTMLEngineProvider #6885
Conversation
# Conflicts: # src/components/HTMLEngineProvider/BaseHTMLEngineProvider.js
# Conflicts: # src/components/HTMLEngineProvider/BaseHTMLEngineProvider.js
Merged main again to keep up-to-date and make sure tests pass, but there were no conflicts. Small bump @stitesExpensify |
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.
LGTM, good cleanup IMO!
✋ 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 @stitesExpensify in version: 1.1.31-2 🚀
|
🚀 Deployed to production by @AndrewGable in version: 1.1.32-0 🚀
|
Details
This PR cleans up the
HTMLEngineProvider
component implementation to make it align with the one-component-per-file convention we have throughout the rest of our codebase. There was a seemingly arbitrary exception made inHTMLEngineProvider
, and it made the component very large and harder to scan/reason about.Fixed Issues
$ n/a
Tests
QA Steps
Just regression tests.
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android