-
Notifications
You must be signed in to change notification settings - Fork 0
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
[EMBR-4352] Run Swiftlint/Clang-format over RN iOS module #83
Conversation
8fe6dd7
to
8e32a86
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #83 +/- ##
=======================================
Coverage 78.56% 78.56%
=======================================
Files 28 28
Lines 1241 1241
Branches 99 92 -7
=======================================
Hits 975 975
Misses 266 266
|
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, I think this would be good to hook up to the github workflow as well
when merging 5.0 we should remember remove the extra .swiftlint.yml
files added there
"publish-modules": "npx lerna run build && npx lerna publish", | ||
"build": "npx lerna run build", | ||
"test": "jest", | ||
"lint": "eslint . --ext .js,.jsx,.ts,.tsx --fix && prettier --write \"**/*.{js,jsx,ts,tsx,json}\" && yarn constraints --fix", |
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.
is this regular lint
command still needed given the others we have now?
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.
I don't think so, the only difference is the json
part and honestly I usually do not run this script. I can remove it if doesn't seems to be useful for you as well
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.
ya I think we can just remove
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 one will conflict since we fully changed it on 5.0, might be better to not update as part of this PR
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.
Yes, this is why I would prefer to wait until we make the releases and then after all merge this pr and run linters again
packages/core/scripts/util/ios.ts
Outdated
export const EMBRACE_INIT_OBJECTIVEC = | ||
"[[Embrace sharedInstance] startWithLaunchOptions:launchOptions framework:EMBAppFrameworkReactNative];"; | ||
export const EMBRACE_INIT_OBJECTIVEC = `[[Embrace sharedInstance] startWithLaunchOptions:launchOptions | ||
framework:EMBAppFrameworkReactNative];`; |
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.
I'm not sure about this change, since it's injected into the customer's app delegate I think this will end up including extra whitespace
Dependency ReviewThe following issues were found:
|
Test
UPDATE: previous issue was fixed. Unit tests work fine after tweaks on strings.
Goal
yarn lint:swift
)yarn lint:clang
)yarn lint:js
). NOTE: the baseyarn lint
cover json files, and json files are also into ios/android directories making the plugin to run into the entire project (resulting in unexpected behaviors)