Class | RSCM::Revisions |
In: |
lib/rscm/revisions.rb
|
Parent: | Object |
A Revisions object is a collection of Revision objects with some additional behaviour.
Most importantly, it provides logic to group individual RevisionFile objects into Revision objects internally. This means that implementors of RSCM adapters that don‘t support atomic changesets can still emulate them, simply by adding RevisionFile objects to a Revisions object. Example:
revisions = Revisions.new revisions.add revision_file_1 revisions.add revision_file_2 revisions.add revision_file_3
The added RevisionFile objects will end up in Revision objects grouped by their comment, developer and timestamp. A set of RevisionFile object with identical developer and message will end up in the same Revision provided their time attributes are a minute apart or less.
Each Revisions object also has an attribute cmd which should contain the command used to retrieve the revision data and populate it. This is useful for debugging an RSCM adapter that might behaving incorrectly. Keep in mind that it is the responsibility of each RSCM adapter implementation to set this attribute, and that it should omit setting it if the store_revisions_command is true
cmd | [RW] |
# File lib/rscm/revisions.rb, line 34 34: def initialize(revisions=[]) 35: @revisions = revisions 36: end
# File lib/rscm/revisions.rb, line 38 38: def add(file_or_revision) 39: if(file_or_revision.is_a?(Revision)) 40: @revisions << file_or_revision 41: else 42: revision = find { |a_revision| a_revision.accept?(file_or_revision) } 43: if(revision.nil?) 44: revision = Revision.new 45: @revisions << revision 46: end 47: revision.add file_or_revision 48: end 49: end