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

Should fastlane be public dependency? #482

Open
mokagio opened this issue May 16, 2023 · 0 comments
Open

Should fastlane be public dependency? #482

mokagio opened this issue May 16, 2023 · 0 comments

Comments

@mokagio
Copy link
Contributor

mokagio commented May 16, 2023

Currently, fastlane is a development dependency to this gem:

spec.add_development_dependency 'fastlane', '~> 2.210'

I haven't verified whether there's a rationale behind it or if it's the default behavior when Fastlane creates a plugin, but I think it would be more appropriate to make it a public dependency.

I run into this in setting up a new project. I though it would have been enough to add the plugin to get access to Fastlane, but that wasn't the case. I found that inconvenient, because I now had to specify two gems instead of one.

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

No branches or pull requests

1 participant