I do most of my work on topic branches and then merge that into a development branch, leaving master as the release candidate branch, hence why the last commit is to add develop to Travis-CI (for my convenience). It's a pretty standard Git workflow nowadays, and shouldn't affect anything until you add a develop branch (which I would advocate) but feel free to skip that commit if it doesn't suit you.
The other commits are just a little bit of clean up in the code, nothing drastic.
Shortened, it's clearer.
Refactored to shorten, remove rescues, and clarify.
Pre-check development branch.
No need for explicit returns.
Because the formatting is confusing.
Make sure the correct String class is picked up by being explicit.
Should accept anything that is String-like. Will be more flexible, al…
…lowing other kinds of enumberable objects like streams/arrays in future too.
Removed multiple assignment statements, not necessary.
Merge branch 'refactor-shell-plugin-entry' into develop
Cleaned up some circular requires; removed unnecessary autoloads; rem…
…oved duplication; squashed superclass mismatch error.
Merge branch 'clean-up-requires-and-compat-in-sequence' into develop
I'm continuing with refactoring the internals, so this pull will become less minor with time :) Cherry pick what you want, but I'll only push to this branch was passes the tests.
Fixed the stack level too deep errors by using Hash#invert.
Early return clearer and idiomatic.
Shorter, clearer, and more idiomatic using the Weirich fail.
Cut out unnecessary logic.
Some commits are merged.
"Refactored to shorten, remove rescues, and clarify" is committed as 08dd928
"Fixed the stack level too deep errors by using Hash#invert" is committed as c229a20
"Early return clearer and idiomatic" is committed as 5f3569f
"Corrected spelling" is committed as 888a705
* fix typo. Thanks to Iain Barnett who reported the bug in
Some commits are not merged.
Using absolute file path to require file is not a solution of circular require. Circular require can occur even if absolute file path is used.
It's been a while since I did those commits, but from looking at it, I'm not trying to solve the circular require by using absolute paths but by moving where the requires are called. The absolute paths is because I really wanted to use require_relative but Ruby v1.8 is still being supported which doesn't have them, so using the absolute path is the nearest thing without bringing in a gem or some extra code to handle it.
Hope that clears it up.
@yb66 Thank you for explanation. BioRuby 1.5 will be the final version to support Ruby 1.8.