-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[camera] Fix type casing #26900
[camera] Fix type casing #26900
Conversation
c00f5c0
to
db667ac
Compare
@@ -1,3 +1,3 @@ | |||
{ | |||
"expo.jsEngine": "jsc" | |||
"expo.jsEngine": "hermes" |
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.
Any specific reason why we changed this? As far as I remember we don't use JS at all in this app
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 Shared object tests were failing on jsc. I bumped the Xcode version and switched to Hermes and it worked a lot better. I think we went back to Xcode 14 so maybe this needs to be changed but might have the same issue with the tests.
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.
Imho we should switch it back to JSC, for these reasons:
- it wouldn't need to download and link hermes (faster build, but probably not that much since it's no longer built from sources)
- we don't test JSC at all since we added support for Hermes, so I intentionally used JSC here to at least have some small coverage 😅
I know these tests started failing at some point, but I think we should fix that issue instead of changing the engine.
Why
Closes ENG-11235
The casing on everything related to barcodes was inconsistent causing problems with autocomplete
How
Fixed all instances of
Barcode
in the next package to be consistentTest Plan