-
Notifications
You must be signed in to change notification settings - Fork 986
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
refactor: do not infer project root from script location #1202
Conversation
for better or worse...
That change seems unrelated to the scope of this PR. Moreover, it seems we could delete the whole following conditional as well, since we removed support for the platform-centric workflow.
logPath was "$cordovaPath/console.log" before and had been changed to "$projectPath/console.log". This commit reverts that change.
Not pretty either, but at least the ugliness is more local
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 pushed a few commits with suggestions. Explanations are in the respective commit messages. Otherwise these changes look good to me!
The added test mentioned in the PR comment is not here, but that's OK. I take it that you just copied the text from my corresponding android PR? 😁 |
Codecov Report
@@ Coverage Diff @@
## master #1202 +/- ##
==========================================
- Coverage 75.15% 75.09% -0.07%
==========================================
Files 13 13
Lines 1658 1658
==========================================
- Hits 1246 1245 -1
- Misses 412 413 +1
Continue to review full report at Codecov.
|
Co-authored-by: Raphael von der Grün <raphinesse@gmail.com>
Motivation and Context
The goal of this PR is to eliminate all areas where our JS library expects to be located inside the project directory.
This is to prepare for a change that will keep the library in
node_modules
and not copy it to the platform project.Description
Basically this passes the project root that has been passed to
Api
to all places that need it but do not yet have it.This also extends the E2E tests to check that we do not have to require the Api from the platform project folder.Testing
npm t
Checklist