kotovalexarian-likes-github/awesome_print
1
0
Fork 0
mirror of https://github.com/awesome-print/awesome_print synced 2023-03-27 23:22:34 -04:00
Code Releases Activity
awesome_print/CHANGELOG.md

169 lines
7.9 KiB
Markdown
Raw Normal View History

Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## master (unreleased)
Fixes block and proc definition to work with Ruby 3.0.0 (#392)
2021-01-12 21:03:16 -05:00
- Fixes block and proc definition to work with Ruby 3.0.0 [@csalvato] - [#392]
Retire eol rubies (#393) * Removed rubys 2.4 and earlier * Updated docs with changes Co-authored-by: Bryan Hanks, PMP <bryan@master-developer.com>
2021-01-12 20:08:40 -05:00
- Removed check for Ruby 2.4 and earlier [@bryanh]
- Rails 5.0 builds are failing, because the sqlite3 version being installed is wrong version [#366]
Add changelog notes in the prep for next release
2019-01-09 10:42:43 -05:00
- Fixes spec suite to properly work via travis, gets a clean build [@imajes, others]
- Adds support for ActiveModel::Errors [@dshinzie] - [#301]
- removes use of `strip_heredoc` from specs as it's a rails dep [@kstephens] - [#303]
ArrayFormatter now returns arrays for has_many :through associations The array_formatter was always returning an empty array when associated objects were called via a `has_many through:` relationship because they are loaded as a collection, and the collection is always considered empty. resolves: https://github.com/awesome-print/awesome_print/issues/331
2018-02-03 19:11:08 -05:00
- ArrayFormatter now returns arrays for has_many :through associations [@chadh13] - [#332]
Bump 1.8.0
2017-06-16 17:22:56 -04:00
## 1.8.0
stat("$HOME/.aprc") only once per process.
2017-03-06 10:55:56 -05:00
- stat("$HOME/.aprc") once [@kstephens] - [#304]
ActiveRecord awesome #joins: now shows the #select'ed columns
2015-12-01 17:38:15 -05:00
- ActiveRecord: #joins now show the columns #select'ed [@adrianomitre] - [#211]
Handle NoMethodError for IRB implicit #ai
2015-12-18 19:12:14 -05:00
- Handles NoMethodError for IRB implicit `ai` [@jtnegrotto] - [#212]
Retire eol rubies (#393) * Removed rubys 2.4 and earlier * Updated docs with changes Co-authored-by: Bryan Hanks, PMP <bryan@master-developer.com>
2021-01-12 20:08:40 -05:00
- Replaced Fixnum reference with Integer
Colorize ORM class names
2016-02-11 18:50:31 -05:00
- Colorize ORM class names [@ixti]
1.7.0 version bump for release
2016-06-06 12:52:15 -04:00
## 1.7.0
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
- Refactoring by extracting formatters into their own classes [@waldyr] - [#237]
- Fixes Travis builds and improves tests [@nviennot], [@waldyr], [@gerrywastaken] - [#225], [#228], [#229], [#230], [#231]
- Creates `awesome_object_data` to encapsulate the logic of printing object internals,
so Structs and Objects can be printed as one [@waldyr] - [#226]
- Fixes development dependencies for environments without rake [@aleandros], [@cyberdelia] - [#222], [#216]
- Documents `ai` method usage [@MaxPleaner] - [#217]
- Fixes conflict with `mail` and other gems which fake ActiveSupport [@kemmason] - [#200]
- Improves spec performance and simplicity [@maurogeorge]
- Handle objects that have a custom #to_hash method [@clonezone]
## 1.6.1
Bumps version and cleans up CHANGELOG
2014-12-31 13:48:58 -05:00
- Fixes specs on all rails dependencies (Mauro George)
- Updates specs for mongoid, mongo_mapper and ripple (James Cox)
- Adds appraisals for simpler version/scenario management (Mauro George)
Updates documentation and utilize social tools Create CONTRIBUTING file Add rubygems badge Add code climate badge Add badge of total of downloads Add badges flat style Add changelog of the changes Add info about how to use appraisal Fix link to changelog on CONTRIBUTING Add Semantic Version on the README
2014-12-31 10:15:32 -05:00
- Add Travis (Mauro George)
Bumps version and cleans up CHANGELOG
2014-12-31 13:48:58 -05:00
- Update documentation (Mauro George)
Updates documentation and utilize social tools Create CONTRIBUTING file Add rubygems badge Add code climate badge Add badge of total of downloads Add badges flat style Add changelog of the changes Add info about how to use appraisal Fix link to changelog on CONTRIBUTING Add Semantic Version on the README
2014-12-31 10:15:32 -05:00
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 1.6.0
Update Changelog for release
2014-12-29 12:50:31 -05:00
semi-major release since it's been a while, and there are several
improvements.
- Improves support for new mongoid/moped (Velkitor, Francois Bernier et al)
- Converts specs to rspec 3+ (Adam Jonas, James Cox)
- Fixes incompatibility with IPAddr (James Cox, Michael Dvorkin)
- Fixes incompatibility with the money gem (Michael Dvorkin)
- Fixes AR::Relation presentation (Sergey Ponomarov)
- Lazy-loads ActionView (Akira Matsuda)
- Fixes inspection of abstract classes (Jonathan Priddle)
- Gets most specs passing, and fixes suite (Eoin Kelly)
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 1.2.0
#### NOTE: This is the *last* release supporting Ruby < v1.9.3 and Rails < v3.
Updated CHANGELOG for 1.2.0 release
2013-09-20 00:38:28 -04:00
- Added Sequel ORM plugin (Jonathan Davies)
- Added Ripple plugin (Ruby modeling layer for Riak, Scott Hyndman)
- Added NoBrainer plugin (Ruby ORM for RethinkDB, Nicolas Viennot)
- Added formatting for Ruby set objects (Richard Hall)
- Fixed HTML formatting (Mike McQuaid)
- Other minor bugs and enhancements
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 1.1.0
Updated CHANGELOG
2012-09-11 19:11:27 -04:00
- Objects are no longer recursively formatted by default. Reenable by using :raw => true option.
- ap(object) now returns nil when running under IRB or Pry
- Added support for Mongoid 3 and Moped (Nikolaj Nikolajsen)
- Improved formatting of MongoMapper objects (George .)
- ActiveRecord::Relation now renders as array (Dan Lynn)
- Formatting BigDecimal no longer looses precision (Evan Senter)
- Added AwesomePrint.irb! and AwesomePrint.pry! convenience methods
- Fixed conflict with the colorize gem
- Misc tweaks and bug fixes
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 1.0.2
Updated README and CHANGELOG
2011-12-20 23:04:07 -05:00
- Added formatting of Mongoid documents (Adam Doppelt)
- ActiveRecord objects display attributes only. Use :raw => true to display the entire object
- ActiveSupport::Date objects get formatted as regular Date
- Rails.logger.ap colorizes output based on ActiveSupport::LogSubscriber.colorize_logging (default is true)
- Improved formatting of methods array
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 1.0.1
Release 1.0.1
2011-11-30 00:16:05 -05:00
- Updated repo tags for Rubygems.org
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 1.0.0 Thanksgiving edition
Updated README and CHANGELOG
2011-06-02 01:51:45 -04:00
- Added ability to format *arbitrary* Ruby object
- Added :limit option to limit large output for arrays and hashes (Andrew Horsman)
Updated README and CHANGELOG files
2011-11-29 23:26:00 -05:00
- Improved HTML formatting when :html => true (Daniel Johnson)
- Added Mongoid extension (Adam Doppelt)
- Added Nokogiri extension (Adam Doppelt)
- Removed Jeweler gem dependency
Updated README and CHANGELOG
2011-06-02 01:51:45 -04:00
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.4.0
Getting ready for 0.4.0 release
2011-05-13 18:10:06 -04:00
- 'ap object' now returns the object (Stephan Hagemann)
- Added :html => true option to enable HTML colors rather that ANSI (ex. Sinatra templates)
- Added AwesomePrint.force_colors! to allow color output on demand (Andrew O'Brien)
- Added MongoMapper formatter mixin (Elpizo Choi)
- Fixed formatting of methods array when object#method is overridden
- Fixed potential stack errors by checking whether AwesomePrint is already loaded
- Improved Ruby 1.8.6 and 1.8.7 compatibility
- Improved Windows compatibility (Viktar Basharymau)
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.3.2
Getting ready for 0.3.2 release
2011-02-03 01:43:55 -05:00
- Make sure Rails mixins get loaded in Rails console when required from .irbrc
Fixed an issue with classes that define their own #send method (ex: Socket); fixed compatibility issue with Liquid gem
2011-01-27 22:51:17 -05:00
- Fixed an issue with classes that define their own #send method (ex: Socket)
- Fixed compatibility issue with Liquid gem that defines Module#liquid_methods
- Fixed hash spec for Ruby < 1.9 where order of hash keys is not guaranteed
Getting ready for 0.3.2 release
2011-02-03 01:43:55 -05:00
- Added :sorted_hash_keys option to sort hash keys (Ed Ruder)
Fixed an issue with classes that define their own #send method (ex: Socket); fixed compatibility issue with Liquid gem
2011-01-27 22:51:17 -05:00
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.3.1 RubyConf X edition
Updated CHANGELOG and README
2010-11-13 12:49:24 -05:00
- Fixed Ruby 1.8.6 compatibility issues (thanks, Tim!)
- Fixed stack overflow issue with Rails 2.3.x console
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.3.0
Updated README and CHANGELOG files
2010-11-06 19:01:38 -04:00
- Display object.methods and family in human readable format
- Objects inherited from Array, Hash, File, Dir, and Struct are shown as their base class
- Added option to suppress array index in output (Sean Gallagher)
- Updated README on how to set up ~/.irbrc for MacRuby (Eloy Duran)
- Specs pass 100% with Ruby 1.8.7/RSpec 1.3 and Ruby 1.9.2/RSpec 2.0
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.2.1
Release 0.2.1
2010-06-03 22:53:47 -04:00
- ap can now be used within Rails templates (ex. <%= ap object %>)
- Added support for printing Struct
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.2.0
Shell escape file and directory names, README updates
2010-05-06 00:30:00 -04:00
- Added support for logger.ap (including Rails logger)
Release 0.2.0
2010-05-06 01:23:18 -04:00
- Added support for HashWithIndifferentAccess from ActiveSupport
Shell escape file and directory names, README updates
2010-05-06 00:30:00 -04:00
- ap now works with scripts that use ActiveRecord/ActiveSupport outside Rails
- ap now correctly shows file and directory names with fancy characters (shell escape)
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.1.4
Release 0.1.4
2010-04-08 23:40:38 -04:00
- Format BigDecimal and Rational objects as Float scalars
- Explicit options parameter can override custom defaults
- Custom defaults are not interfering when running specs
- Custom defaults now work correctly with Ruby 1.9.x
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.1.3
Added support for setting custom defaults in ~/.aprc
2010-04-08 00:31:21 -04:00
- Added support for setting custom defaults in ~/.aprc
Updates documentation and utilize social tools Create CONTRIBUTING file Add rubygems badge Add code climate badge Add badge of total of downloads Add badges flat style Add changelog of the changes Add info about how to use appraisal Fix link to changelog on CONTRIBUTING Add Semantic Version on the README
2014-12-31 10:15:32 -05:00
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.1.2
Added support for setting custom defaults in ~/.aprc
2010-04-08 00:31:21 -04:00
- Correctly handle empty arrays and hashes
- Use alias_method instead of alias (fixes non-tty method aliasing)
- Added awesome_inspect method
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.1.1
Added support for setting custom defaults in ~/.aprc
2010-04-08 00:31:21 -04:00
- Added support for tableless ActiveRecord models
- Left align hash keys if @options[:indent] is negative
Updates documentation and utilize social tools Create CONTRIBUTING file Add rubygems badge Add code climate badge Add badge of total of downloads Add badges flat style Add changelog of the changes Add info about how to use appraisal Fix link to changelog on CONTRIBUTING Add Semantic Version on the README
2014-12-31 10:15:32 -05:00
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
## 0.1.0
Added support for setting custom defaults in ~/.aprc
2010-04-08 00:31:21 -04:00
- Initial Release.
Updates documentation and utilize social tools Create CONTRIBUTING file Add rubygems badge Add code climate badge Add badge of total of downloads Add badges flat style Add changelog of the changes Add info about how to use appraisal Fix link to changelog on CONTRIBUTING Add Semantic Version on the README
2014-12-31 10:15:32 -05:00
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
[#200]: https://github.com/awesome-print/awesome_print/pull/200
Handle NoMethodError for IRB implicit #ai
2015-12-18 19:12:14 -05:00
[#212]: https://github.com/awesome-print/awesome_print/pull/212
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
[#216]: https://github.com/awesome-print/awesome_print/pull/216
[#217]: https://github.com/awesome-print/awesome_print/pull/217
[#222]: https://github.com/awesome-print/awesome_print/pull/222
[#225]: https://github.com/awesome-print/awesome_print/pull/225
[#226]: https://github.com/awesome-print/awesome_print/pull/226
[#228]: https://github.com/awesome-print/awesome_print/pull/228
[#229]: https://github.com/awesome-print/awesome_print/pull/229
[#230]: https://github.com/awesome-print/awesome_print/pull/230
[#231]: https://github.com/awesome-print/awesome_print/pull/231
[#232]: https://github.com/awesome-print/awesome_print/pull/232
[#237]: https://github.com/awesome-print/awesome_print/pull/237
[@aleandros]: https://github.com/aleandros
[@clonezone]: https://github.com/clonezone
[@cyberdelia]: https://github.com/cyberdelia
[@gerrywastaken]: https://github.com/gerrywastaken
Colorize ORM class names
2016-02-11 18:50:31 -05:00
[@ixti]: https://github.com/ixti
Handle NoMethodError for IRB implicit #ai
2015-12-18 19:12:14 -05:00
[@jtnegrotto]: https://github.com/jtnegrotto
Update changelog for the next release I've also started adding links to the associated pull requests and authors. The intention is to make it easier to find the origin of a change. The repetitive nature of the references annoys me, but unfortunately I don't believe there is a cleaner way to do this in markdown. If you can think of a solution, then please let us know. I've cleaned up some of the wording so the gramar is consistent and sorted the changes from newest to oldest so that it's consistent with the newest to oldest ordering of the version numbers. I've only made these changes for the latest commits, however if somebody wishes to go back and add links for older changes, that be a pull request I would happily merge.
2016-06-06 11:16:47 -04:00
[@kemmason]: https://github.com/kemmason
[@maurogeorge]: https://github.com/maurogeorge
[@MaxPleaner]: https://github.com/MaxPleaner
[@nviennot]: https://github.com/nviennot
[@waldyr]: https://github.com/waldyr
Copy permalink