-
Notifications
You must be signed in to change notification settings - Fork 561
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
fix: fix combination of rubygems and --all-projects #2333
Conversation
|
ed4dffd
to
5706ef8
Compare
today all rebygems projects have the same project name with --all-projects flag. this adds the nested dir name into the project name.
5706ef8
to
5fef84f
Compare
|
||
export async function inspect( | ||
root: string, | ||
targetFile: string, | ||
options: types.Options = {}, |
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.
We already send the options when we run inspect
, but never used it here.
All changes in this file is just to propagate options
to the plugin
return { | ||
packageName: path.basename(root), | ||
packageName: options.allSubProjects |
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.
Because the name of the package here is the actual name of the project, and the project name is a part of the identifier, we only want to change this in the problematic area we're facing of 2 or more projects with the '--all-projects` flag.
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.
nice one @admons 🕺
What does this PR do?
today all rebygems projects have the same project name with --all-projects flag.
this adds the nested dir name into the project name.