Skip to content
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

Run extension with a custom Firefox binary #105

Merged
merged 1 commit into from
Mar 4, 2016

Conversation

kumar303
Copy link
Contributor

@kumar303 kumar303 commented Mar 3, 2016

Fixes #71

Some other things:

  • Moved cli.js into program.js because all this logic is related
  • Added missing tests for temp-dir.js
  • Improved coverage of the main() program code
  • Fixed up option handling since this feature required command sub-options for the first time
  • Regressed static coverage of handler options, to be addressed in Protect commands from using the wrong options #106
  • Made --build-dir specific to build rather than a global option

@kumar303 kumar303 force-pushed the custom-firefox branch 6 times, most recently from 51db667 to 07ac6da Compare March 4, 2016 00:01
@kumar303
Copy link
Contributor Author

kumar303 commented Mar 4, 2016

@rpl could you review?

* Each class instance variable is a camel case expanded program
* option. Each option is defined in program.yargs.option(...).
*/
export class ProgramOptions {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed this because it wasn't working (too many errors I could not resolve). I filed #106 to look for a solution.

@kumar303 kumar303 force-pushed the custom-firefox branch 2 times, most recently from 533531d to be61c02 Compare March 4, 2016 17:03
/* @flow */
import build from './build';
import run from './run';
export {build, run};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably a good candidate for an `export default {build, run}'.

if we do this kind of change, we need to change the corresponding imports [1] to something like:

import defaultCommands from  './cmd';

[1]: in https://github.com/mozilla/web-ext/pull/105/files#diff-9589e3a0cc72e26a4814bc9ef05aa2d4R6
and
in https://github.com/mozilla/web-ext/pull/105/files#diff-2d9bd4ae7220a18dfa5b6b6707f45213R7

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, good idea. I didn't know that was possible :)

@rpl
Copy link
Member

rpl commented Mar 4, 2016

@kumar303 looks great

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants