You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That sounds like we might need a configuration option of some kind to set the type to assign to gemfile deps... or maybe the "type" we assign to Gemfile packages by default shouldn't be dev vs. runtime at all but more something noncommittal like "gemfile" or "unknown", and then it can be configured? Or possibly a default like runtime is more useful, as long as it can be corrected via config for libraries.
If this library is used also for final applications, the I'd say you need to detect whether you're analyzing a library or an application, and then act accordingly. If this library is only be meant to be used by libraries, then would anyhing break if you assign "development" instead of "runtime" to all dependencies coming from the Gemfile?
https://github.com/librariesio/bibliothecary/blob/master/lib/bibliothecary/parsers/rubygems.rb#L38
How could we do better here?
The text was updated successfully, but these errors were encountered: