-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Shows a warning when adding a version-less plugin from a path. #1021
Conversation
I'm:
Strawman-mode Engage!So, run this: See that yellow warning in the middle? As a person building a new React Native project, that's meaningless. Here's the same thing with So, if I was given the power to What I need is for upstream to fix their stuff. I don't even know how far upstream either. Jump To Conclusions MatAnd, so this is what this PR is bringing to the table, forcing info on end-users where no action can be taken. Recommendations
I could be convinced (or at least be upgraded to 😐 ) to keep the warning (if the wording was more along the lines of
|
I'm all with you on this, @skellock, makes sense. I thought you were for the warning, though...? |
I thought i was too. |
src/extensions/ignite/addModule.js
Outdated
context.print.warning(`Plugin should specify specific version for NPM module ${moduleName} in addModule call.`) | ||
context.print.warning(`Please add version: "<version here>" or to suppress this warning, pass in yolo: true`) | ||
} | ||
return moduleName |
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.
dem multiple returns :)
@skellock knows my skin crawled just now.
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.
Okay, okay, I'll change it. 🙄
Sidenote: I like multiple returns -- short circuit the rest of the function if it's not necessary, like a guard statement.
But I'm not dogmatic about it. I don't want your skin crawling. 😁
I think we're saying "warning" so we can do a deprecation phase. I'm fine if it says what @skellock says, but we need something to identify it's not ok... other than just forcing it. Or maybe we just force it? |
…ath, like a plugin author might
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.
very nice
That's a good compromise. Thank you. |
Fixes #1006.