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

Make pioneer widgets modular #308

Open
buob opened this issue Feb 13, 2015 · 5 comments
Open

Make pioneer widgets modular #308

buob opened this issue Feb 13, 2015 · 5 comments

Comments

@buob
Copy link

buob commented Feb 13, 2015

I want to be able to require a certain class outside of cucumber

@samccone
Copy link
Contributor

yes, we talked about how to do this IRL, it will require a change to the pioneer build phase and a but of shuffling around of the classes, however it should not be so hard. @buob are you interested in doing this?

@buob
Copy link
Author

buob commented Feb 13, 2015

Sure. Let's leave it unassigned for now though in case someone else gets to it before I do.

@samccone
Copy link
Contributor

Would you like to outline the approach here so that someone else could possibly pick this up. Currently the issue does not really explain the Why or How very well.

@buob
Copy link
Author

buob commented Feb 24, 2015

Why?

The most valuable part of pioneer is the widget abstraction. I should be able to use that separate from all of the runner, gherkin, etc. pieces. For example, in my plain old javascript file, something like:

module.exports = require('pioneer/widget').extend({
    root: '.foo',

    welcomeMessage: function() {
      return this.find('.welcome');
    }
});

How?

Alter the build so that it builds each component separately, and then in the cucumber side of things, require those and invoke them.

@samccone
Copy link
Contributor

yep 👍 this is the way to do it

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

No branches or pull requests

2 participants