aboutsummaryrefslogtreecommitdiffstats
path: root/.codeclimate.yml
diff options
context:
space:
mode:
authorHomu <homu@barosl.com>2016-07-26 22:50:21 +0900
committerHomu <homu@barosl.com>2016-07-26 22:50:21 +0900
commit6904ac6872be56290b12088a6595480de2ae9c53 (patch)
treede6dff8b7eb6cd92487770a5d1de168540f1a722 /.codeclimate.yml
parent2b649723dc7730b79df7dee3837afcff949f3d3a (diff)
parent8b59481c9fb11d8273ff7606593682dfeabd7dd9 (diff)
downloadbundler-6904ac6872be56290b12088a6595480de2ae9c53.tar.gz
Auto merge of #4811 - NickLaMuro:dots_for_compact_index_logger, r=segiddins
Fix random string printing inconsistencies and formatting Add dot output for CompactIndex fetcher --------------------------------------- The `Bundler::Fetcher::CompactIndex`'s logging was missing the "dot logging" when not in debug mode, which is an assumed behavior based on the code in `lib/bundler/source/rubygems.rb`: ```ruby api_fetchers.each do |f| Bundler.ui.info "Fetching gem metadata from #{f.uri}", Bundler.ui.debug? idx.use f.specs_with_retry(dependency_names, self) Bundler.ui.info "" unless Bundler.ui.debug? # new line now that the dots are over end ``` While this isn't critical for `bundler` function properly by any stretch of the imagination, it provides a small bit of user feedback that requests are still continuing to be processed and `bundler` hasn't stalled. It also maintains logging consistency between the different fetcher models. Add newlines for `Bundler::Retry` --------------------------------- This is very pedantic, but it makes it so that retry warning messages that used to look like this: ``` Fetching gem metadata from https://rubygems.org/....Retrying fetcher due to error (2/4): Error::OMGWatHappened LOL, no idea ..... ``` Now will look like this: ``` Fetching gem metadata from https://rubygems.org/.... Retrying fetcher due to error (2/4): Error::OMGWatHappened LOL, no idea..... ``` I think this reads a bit better and puts context to the "dots" so they now match up with the original attempt and the retries Remove unneeded if statement ---------------------------- Ran across this while failing at writing tests for the above (for longer than I want to admit in public), but basically the `if` statement to determine whether or not to print "name" in the `Bundler.ui.warn` was not needed, as it never could be reached because of a short circuiting return statement prior to the print ```ruby return true unless name ``` Have no idea how to test it anymore than we already are, so instead of embarrassing myself further, I moved on.
Diffstat (limited to '.codeclimate.yml')
0 files changed, 0 insertions, 0 deletions