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
Update parser and logging to handle log spy #6671
Conversation
…'t actually have values
weird, my editor must not have caught these. will fix. |
@@ -6,7 +6,7 @@ import logger from './logger'; // logger needs to remain first of imports | |||
import _ from 'lodash'; | |||
import { server as baseServer } from 'appium-base-driver'; | |||
import { asyncify } from 'asyncbox'; | |||
import getParser from './parser'; | |||
import getParser, { getDefaultArgs } from './parser'; |
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 works?
I've always used import { default as getParser, getDefaultArgs } from './parser';
@imurchie you're right that was it. it did work, however jshint blows up on it so i changed it. and welp. somehow i broke my feature. fixing. |
… on logs this is necessary for the new appium desktop
…t was undefined in places
@imurchie ok everything passes locally and hopefully will on CI this time |
\o/ looks like Travis passed, looking for a merge whenever you're happy @imurchie |
Looks good to me! |
The new appium desktop will import Appium and run it in memory, so we need a way to attach a log spy method.
Some other cleanup as well along the way.
This is the branch that is currently supporting the work in progress at https://github.com/jlipps/appium-desktop (using
npm link
)