The TRB book makes heavy use of Cell::Concept, and I wasn't sure what the difference is between this and Cell::ViewModel or Trailblazer::Cell... and on having a look in the source, I spotted this easy-to-miss comment.
Cell::Concept is no longer under active development. Please switch to Trailblazer::Cell.
This PR makes this warning more obvious by moving it from a comment to a puts statement when you initialize a new Cell::Concept. I realise that putting this in the initialize method isn't ideal, but Ruby's own deprecate method requires you to specify a specific method that's deprecated rather than deprecating the class as a whole. (None of the answers to this SO question really strike me as great solutions to the 'how do I deprecate an entire class?' question.)
Apologies if this class isn't actually "deprecated" in the sense that you're planning on removing it (as opposed to leaving it in there but not continuing active development on it.)
The TRB book makes heavy use of
Cell::Concept
, and I wasn't sure what the difference is between this andCell::ViewModel
orTrailblazer::Cell
... and on having a look in the source, I spotted this easy-to-miss comment.This PR makes this warning more obvious by moving it from a comment to a
puts
statement when you initialize a newCell::Concept
. I realise that putting this in theinitialize
method isn't ideal, but Ruby's owndeprecate
method requires you to specify a specific method that's deprecated rather than deprecating the class as a whole. (None of the answers to this SO question really strike me as great solutions to the 'how do I deprecate an entire class?' question.)Apologies if this class isn't actually "deprecated" in the sense that you're planning on removing it (as opposed to leaving it in there but not continuing active development on it.)