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

Cucumber component generator fails #1567

Closed
fgarcia opened this Issue Jan 30, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@fgarcia

fgarcia commented Jan 30, 2014

The Cucumber component generation looks OK if I generate a new project:

padrino g project testapp --test cucumber

However adding Cucumber to an already built project doesn't

padrino g component --test cucumber

The difference lies in the generated features/support/env.rb

Capybara.app = Testapp::.tap { |app| }

Only in the second case (after project has been generated) Padrino misses the "App" in what should be Test::App.tap

(Padrino v. 0.11.4)

@namusyaka

This comment has been minimized.

Show comment
Hide comment
@namusyaka

namusyaka Jan 30, 2014

Member

I created a pull request. Could you try this?

Member

namusyaka commented Jan 30, 2014

I created a pull request. Could you try this?

@namusyaka namusyaka closed this in c255af0 Jan 31, 2014

ujifgc added a commit that referenced this issue Jan 31, 2014

Merge pull request #1568 from padrino/fix-component-generator
Add :app option to the component generator, fixes #1567
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment