pod4 0.7.1 → 0.7.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3413f940c1247aeff8c31bc7498b3a5d03f0a63a
-  data.tar.gz: ca5ba62daf452817d7b95131af0b581b940e06e5
+  metadata.gz: 9c0490f9b2e4082a0d36fde99281b5ec3b18dc06
+  data.tar.gz: 5338ef5d4695a2b0385a0093e43f4e4658c580c6
 SHA512:
-  metadata.gz: f40df06b6b359502f201d9eae2e7a2970d96ace5166bd6932b2ea4b2b7d8e0109aa407b0e95007d2aa0e11730bfa5de420abd236443f6dbc20d2caf278776f03
-  data.tar.gz: d70085fb97f4911dd052a099f7744925eb3f292860819739fbdacc47fc2f196aac8ccb9e34944d9e405b04a8a1480b08fce7c6215546f23be682e0ab67806ce3
+  metadata.gz: 21795d227c37d1a80d6d60a0a74f9c5111818cd80dcc696e2fc77641bbcbba9d1f089ab5ec44302825861d5aff0a6e8a3111e8c218cfd7beba5d07753ca9f7ed
+  data.tar.gz: ec96c28be57e17385efef6725cf83e402399eeacaa55be1f089139a1a8f6b889e547f5da36f77b255c2b770a4796948698f25fbbda4d9a918951b08dcebfb308

data/.hgtags

@@ -18,3 +18,4 @@ c2743ca54c4b48c6ebe60b948d251b8d2978c90d 0.5.3
 dc22541876279b47dd366ddb44d262775ccdb933 0.6.1
 4a0e392be3499d9edc9cde66dd3b8d37136a0816 0.6.2
 e41769b310f2eaab5f37d285ce9ad8658b689916 0.7.1
+2c28b064a96d4760d124da3f1842242f52f4cc69 0.7.2

data/Gemfile

@@ -1,6 +1,5 @@
 source 'https://rubygems.org'
 
-
 gemspec
 
 
@@ -10,29 +9,28 @@ group :development, :test do
   gem "bundler", "~> 1.11"
   gem "rake",    "~> 10.5"
   gem "rspec",   "~> 3.4"
-
+  gem 'pry'
+  gem "pry-doc"
 
   # For testing
-  gem "sequel",          "~> 4.35"
-  gem "nebulous_stomp" , "~> 2"
+  gem "sequel",         "~> 4.35"
+  gem "nebulous_stomp", "~> 2"
 
-  platforms :mri do
-    gem "sqlite3",         "~> 1.3"
-    gem "tiny_tds",        "~> 0"
-    gem "pg",              "~> 0"
+  platforms :ruby do
+    gem "sqlite3",  "~> 1.3"
+    gem "tiny_tds", "~> 1.0"
+    gem "pg"
   end
 
   platforms :jruby do
     gem "jruby-lint"
-    gem "pg", git: 'git://github.com/headinus/jruby-pg/git', branch: :master
+    gem "pg_jruby"
   end
 
 
   # Development tools
-  platforms :mri do
+  platforms :ruby do
     gem "rdoc"
-    gem "pry"
-    gem "pry-doc"
     gem "ripper-tags"
   end
   

data/lib/pod4/alert.rb

@@ -2,10 +2,10 @@ module Pod4
   
 
   ##
-  # An Alert is an error, warning or note which might be raised in validation
-  # in the model. They are, however, designed to follow all the way through the
-  # controller to the view; you should use them whenever you want to display a
-  # message on the page.
+  # An Alert is an error, warning or note which might be raised in validation in the model. 
+  #
+  # They are, however, designed to follow all the way through the controller to the view; you
+  # should use them whenever you want to display a message on the page.
   #
   class Alert
 
@@ -26,18 +26,17 @@ module Pod4
 
 
     ##
-    # A new alert must have a type (error warning info or success); there
-    # should be a message to display, obviously. Note that you can pass an
-    # exception in place of a message, in which case @exception will be set.
+    # A new alert must have a type (error warning info or success); there should be a message to
+    # display, obviously. Note that you can pass an exception in place of a message, in which case
+    # @exception will be set.
     #
-    # You may optionally specify the name of the field to be highlighted.
-    # Models will give validation alerts a field that corresponds to the model
-    # attribute; but this is not enforced here, and your controller will have
-    # to sort things out if the model is expecting different field names.
+    # You may optionally specify the name of the field to be highlighted. Models will give
+    # validation alerts a field that corresponds to the model attribute; but this is not enforced
+    # here, and your controller will have to sort things out if the model is expecting different
+    # field names.
     #
     def initialize(type, field=nil, message)
-      raise ArgumentError, "unknown alert type" \
-        unless ALERTTYPES.include? type.to_s.to_sym
+      raise ArgumentError, "unknown alert type" unless ALERTTYPES.include? type.to_s.to_sym
 
       @type      = type.to_s.to_sym
       @field     = field ? field.to_sym : nil
@@ -58,8 +57,7 @@ module Pod4
 
 
     ##
-    # An array of Alert is automatically sorted into descending order of
-    # seriousness
+    # An array of Alert is automatically sorted into descending order of seriousness
     #
     def <=>(other)
       ALERTTYPES.index(self.type) <=> ALERTTYPES.index(other.type)
@@ -79,7 +77,6 @@ module Pod4
       self
     end
 
-
   end
   ##
 

data/lib/pod4/basic_model.rb

@@ -9,11 +9,11 @@ module Pod4
 
 
   ##
-  # The ultimate parent of all models. It has an interface, an id, a status, 
-  # and alerts. That's pretty much it.
+  # The ultimate parent of all models. It has an interface, an id, a status, and alerts. That's
+  # pretty much it.
   #
-  # This is useful to the user for weirder models -- for example, where the
-  # datasource records and the model instances don't map one-to-one.
+  # This is useful to the user for weirder models -- for example, where the datasource records and
+  # the model instances don't map one-to-one.
   #
   # See Pod4::Model for documentation about Models.
   #
@@ -34,8 +34,7 @@ module Pod4
     class << self
 
       ##
-      # You MUST call this in your model definition to give it an instance of an
-      # interface. 
+      # You MUST call this in your model definition to give it an instance of an interface. 
       #
       def set_interface(interface)
         define_class_method(:interface) {interface}
@@ -61,8 +60,7 @@ module Pod4
 
 
     ##
-    # Syntactic sugar; same as self.class.interface, which returns the
-    # interface instance.
+    # Syntactic sugar; same as self.class.interface, which returns the interface instance.
     #
     def interface; self.class.interface; end
 
@@ -70,8 +68,7 @@ module Pod4
     ##
     # Return the list of alerts. 
     #
-    # We don't use attr_reader for this because it won't protect an array from
-    # external changes.
+    # We don't use attr_reader for this because it won't protect an array from external changes.
     #
     def alerts; @alerts.dup; end
 
@@ -79,10 +76,9 @@ module Pod4
     ##
     # Clear down the alerts.
     #
-    # Note that set model_status to :okay. Theoretically it might need to be
-    # :empty or :deleted, but if you are calling clear_alerts before a call to
-    # `read` or after a call to `delete`, then you have more problems than I
-    # can solve.
+    # Note that set model_status to :okay. Theoretically it might need to be :empty or :deleted,
+    # but if you are calling clear_alerts before a call to `read` or after a call to `delete`, then
+    # you have more problems than I can solve.
     #
     def clear_alerts
       @alerts       = []
@@ -91,12 +87,12 @@ module Pod4
 
 
     ##
-    # Raise a SwingShift exception for the model if any alerts are status
-    # :error; otherwise do nothing.
+    # Raise a SwingShift exception for the model if any alerts are status :error; otherwise do
+    # nothing.
+    #
+    # Note the alias of or_die for this method, which means that if you have kept to the idiom of
+    # CRUD methods returning self, then you can steal a lick from Perl and say:
     #
-    # Note the alias of or_die for this method, which means that if you have
-    # kept to the idiom of CRUD methods returning self, then you can steal a
-    # lick from Perl and say:
     #     MyModel.new(14).read.or_die
     #
     def raise_exceptions

data/lib/pod4/errors.rb

@@ -16,8 +16,7 @@ module Pod4
   ##
   # Base error class for Swingshift
   #
-  # Also used for any configuration errors where ArgumentError is not
-  # appropriate.
+  # Also used for any configuration errors where ArgumentError is not appropriate.
   #
   class Pod4Error < StandardError
 
@@ -45,8 +44,8 @@ module Pod4
   ##
   # Raised if a Pod4 method runs into problems
   #
-  # Note, invalid parameters get a Ruby ArgumentError. This is for, eg, an
-  # interface finding that the ID it was given to read does not exist.
+  # Note, invalid parameters get a Ruby ArgumentError. This is for, eg, an interface finding that
+  # the ID it was given to read does not exist.
   #
   class CantContinue < Pod4Error
 

data/lib/pod4/interface.rb

@@ -8,25 +8,22 @@ module Pod4
   ##
   # Abstract class, The parent of all interfaces.
   #
-  # An interface encapsulates whatever method we are using up connect to the
-  # data. Its state is therefore that of the connection, not the DB table or
-  # whatever entity that the data source uses to group data. It raises only
-  # SwingShift errors (wrapping the error it gets inside a SwingShift error).
+  # An interface encapsulates whatever method we are using up connect to the data. Its state is
+  # therefore that of the connection, not the DB table or whatever entity that the data source uses
+  # to group data. It raises only SwingShift errors (wrapping the error it gets inside a SwingShift
+  # error).
   #
-  # We would expect a child of Interface for each data access type
-  # (sequelInterface, NebulousInterface, etc). These children *will not change*
-  # the signatures of the methods below.
+  # We would expect a child of Interface for each data access type (sequelInterface,
+  # NebulousInterface, etc). These children *will not change* the signatures of the methods below.
   #
-  # The methods below are the required ones. Interfaces will likely implement
-  # other, interface-specific, ways of accessing data.
+  # The methods below are the required ones. Interfaces will likely implement other,
+  # interface-specific, ways of accessing data.
   #
-  # In Normal use, the interface classes will in turn be subclassed as inner
-  # classes within each model, in order to customise them for the specific
-  # entity that they are drawing data from. 
+  # In Normal use, the interface classes will in turn be subclassed as inner classes within each
+  # model, in order to customise them for the specific entity that they are drawing data from. 
   #
-  # Note that your Interface subclass probably returns an Octothorpe rather
-  # than a Hash, q.v..  (But you should be able to treat the former as if it
-  # were the latter in most cases.)
+  # Note that your Interface subclass probably returns an Octothorpe rather than a Hash, q.v..
+  # (But you should be able to treat the former as if it were the latter in most cases.)
   #
   class Interface
     extend Metaxing
@@ -43,9 +40,9 @@ module Pod4
 
 
     ##
-    # Individual implementations are likely to have very different initialize
-    # methods, which will accept whatever SwingShift object is needed to
-    # contact the data store, eg. the Sequel DB object. 
+    # Individual implementations are likely to have very different initialize methods, which will
+    # accept whatever SwingShift object is needed to contact the data store, eg. the Sequel DB
+    # object. 
     #
     def initialize
       raise NotImplemented, "Interface needs to define an 'initialize' method"
@@ -53,11 +50,10 @@ module Pod4
 
 
     ##
-    # List accepts a parameter as selection criteria, and returns an array of
-    # Octothorpes. Exactly what the selection criteria look like will vary from
-    # interface to interface. So will the contents of the return OT, although
-    # it must include the ID field. (Ideally each element of the return array
-    # should follow the same format as the return value for read(). )
+    # List accepts a parameter as selection criteria, and returns an array of Octothorpes. Exactly
+    # what the selection criteria look like will vary from interface to interface. So will the
+    # contents of the return OT, although it must include the ID field. (Ideally each element of
+    # the return array should follow the same format as the return value for read(). )
     #
     # Note that list should ALWAYS return an array; never nil.
     #
@@ -67,9 +63,8 @@ module Pod4
 
 
     ##
-    # Create accepts a record parameter (Hash or OT, but again, the format of
-    # this will vary) representing a record, and creates the record.  Should
-    # return the ID for the new record.
+    # Create accepts a record parameter (Hash or OT, but again, the format of this will vary)
+    # representing a record, and creates the record.  Should return the ID for the new record.
     #
     def create(record)
       raise NotImplemented, "Interface needs to define 'create' method"
@@ -77,9 +72,8 @@ module Pod4
 
 
     ##
-    # Read accepts an ID, and returns an Octothorpe representing the unique
-    # record for that ID. If there is no record matching the ID then it returns
-    # an empty Octothorpe.
+    # Read accepts an ID, and returns an Octothorpe representing the unique record for that ID. If
+    # there is no record matching the ID then it returns an empty Octothorpe.
     #
     def read(id)
       raise NotImplemented, "Interface needs to define 'read' method"
@@ -87,9 +81,8 @@ module Pod4
 
 
     ##
-    # Update accepts an ID and a record parameter. It updates the record on the
-    # data source that matches the ID using the record parameter.  It returns
-    # self.
+    # Update accepts an ID and a record parameter. It updates the record on the data source that
+    # matches the ID using the record parameter.  It returns self.
     #
     def update(id, record)
       raise NotImplemented, "Interface needs to define 'update' method"

data/lib/pod4/metaxing.rb

@@ -37,24 +37,21 @@ module Pod4
     #     puts Foo.bar   # -> 23
     #     puts MyFoo.bar # -> 42
     # 
-    # This example gives us something different from a class attribute @@bar --
-    # the value of which would be shared between Foo and MyFoo.  And different
-    # again from an attribute @bar on class Foo, which wouldn't turn up in
-    # MyFoo at all. This is a value that has inheritance.
+    # This example gives us something different from a class attribute @@bar -- the value of which
+    # would be shared between Foo and MyFoo.  And different again from an attribute @bar on class
+    # Foo, which wouldn't turn up in MyFoo at all. This is a value that has inheritance.
     #
-    # And this example shows pretty much the only metaprogramming trick you
-    # will find me pulling.  It's enough to do a hell of a lot.
+    # And this example shows pretty much the only metaprogramming trick you will find me pulling.
+    # It's enough to do a hell of a lot.
     #
-    # Note that you need to be very careful what parameters you pass in order
-    # to preserve this inheritance: if you pass a reference to something on
-    # Foo, you will be sharing it with MyFoo, not just inheriting it. Best to
-    # use local variables or dups.
+    # Note that you need to be very careful what parameters you pass in order to preserve this
+    # inheritance: if you pass a reference to something on Foo, you will be sharing it with MyFoo,
+    # not just inheriting it. Best to use local variables or dups.
     #
-    # ...Well, actually, you aren't getting a method on the class -- these are
-    # defined in the class' immediate ancestor, eg, Object. You're getting a
-    # method on the eigenclass, which Ruby inserts between the class' ancestor
-    # and the class. For all of me I can't see a practical difference when it
-    # comes to defining class methods.
+    # ...Well, actually, you aren't getting a method on the class -- these are defined in the
+    # class' immediate ancestor, eg, Object. You're getting a method on the eigenclass, which Ruby
+    # inserts between the class' ancestor and the class. For all of me I can't see a practical
+    # difference when it comes to defining class methods.
     #
     def define_class_method(method, *args, &blk)
       metaclass.send(:define_method, method, *args, &blk)

data/lib/pod4/model.rb

@@ -16,19 +16,19 @@ module Pod4
   #
   # Note that we distinguish between 'models' and 'interfaces':
   #
-  # The model represents the data to your application, in the format that makes
-  # most sense to your application: that might be the same format that it is
-  # stored in on the database, or it might not. The model doesn't care about
-  # where the data comes from. Models are all subclasses of Pod4::Model.
+  # The model represents the data to your application, in the format that makes most sense to your
+  # application: that might be the same format that it is stored in on the database, or it might
+  # not. The model doesn't care about where the data comes from. Models are all subclasses of
+  # Pod4::Model.
   #
-  # An interface encapsulates the connection to whatever is providing the data.
-  # it might be a wrapper for calls to the Sequel ORM, for example. Or it could
-  # be a making a series of calls to a set of Nebulous verbs. It only cares
-  # about dealing with the data source, and it is only called by the model.
+  # An interface encapsulates the connection to whatever is providing the data.# it might be a
+  # wrapper for calls to the Sequel ORM, for example. Or it could be a making a series of calls to
+  # a set of Nebulous verbs. It only cares about dealing with the data source, and it is only
+  # called by the model.
   #
-  # An interface is a seperate class, which is defined for each model. There
-  # are parent classes for most of the data sources you will need, but failing
-  # that, you can always create one from the ultimate parent, Pod4::Interface.
+  # An interface is a seperate class, which is defined for each model. There are parent classes for
+  # most of the data sources you will need, but failing that, you can always create one from the
+  # ultimate parent, Pod4::Interface.
   #
   # Simple Example
   # ---------------
@@ -46,10 +46,9 @@ module Pod4
   #       attr_columns :one, :two, :three
   #     end
   #
-  # In this example we have a model that relies on the Sequel ORM to talk to a
-  # table 'example'. The table has a primary key field 'id' and columns which
-  # correspond to our three attributes one, two and three.  There is no
-  # validation or error control.
+  # In this example we have a model that relies on the Sequel ORM to talk to a table 'example'. The
+  # table has a primary key field 'id' and columns which correspond to our three attributes one,
+  # two and three.  There is no validation or error control.
   #
   # Here is an example of this model in use:
   #     
@@ -66,9 +65,8 @@ module Pod4
   # Overriding Column Representation
   # --------------------------------
   #
-  # If you want to represent information differently on the model than it is
-  # stored on the data source, there are four methods you potentially need to
-  # know about and override:
+  # If you want to represent information differently on the model than it is stored on the data
+  # source, there are four methods you potentially need to know about and override:
   #
   # * set -- used by you to set model column values
   # * to_ot -- used by you to get model column values
@@ -82,10 +80,9 @@ module Pod4
     class << self
 
       ##
-      # You should call this in your model definition to define model 'columns'
-      # -- it gives you exactly the functionality of `attr_accessor` but also
-      # registers the attribute as one that `to_ot`, `map_to_model` and
-      # `map_to_interface` will try to help you with.
+      # You should call this in your model definition to define model 'columns' -- it gives you
+      # exactly the functionality of `attr_accessor` but also registers the attribute as one that
+      # `to_ot`, `map_to_model` and `map_to_interface` will try to help you with.
       #
       def attr_columns(*cols)
         c = columns.dup
@@ -106,15 +103,15 @@ module Pod4
       ##
       # Call this to return an array of record information.
       #
-      # What you actually get depends on the interface, but it must include a
-      # recognisable record ID in each array element.  
+      # What you actually get depends on the interface, but it must include a recognisable record
+      # ID in each array element.  
       #
-      # For the purposes of Model we assume that we can make an instance out of
-      # each array element, and we return an array of instances of the model.
-      # Override this method if that is not true for your Interface.
+      # For the purposes of Model we assume that we can make an instance out of each array element,
+      # and we return an array of instances of the model.# Override this method if that is not true
+      # for your Interface.
       #
-      # Note that list should ALWAYS return an array, and array elements should
-      # always respond to :id -- otherwise we raise a Pod4Error.
+      # Note that list should ALWAYS return an array, and array elements should always respond to
+      # :id -- otherwise we raise a Pod4Error.
       #
       def list(params=nil)
         fail_no_id_fld unless interface.id_fld
@@ -123,7 +120,6 @@ module Pod4
           key = ot[interface.id_fld]; fail_no_id unless key
 
           rec = self.new(key)
-
           rec.map_to_model(ot) # seperately, in case model forgot to return self
           rec 
         end
@@ -132,18 +128,14 @@ module Pod4
 
 
       def test_for_octo(param)
-        raise( ArgumentError, 
-               'Parameter must be a Hash or Octothorpe',
-               caller ) \
+        raise( ArgumentError, 'Parameter must be a Hash or Octothorpe', caller ) \
           unless param.kind_of?(Hash) || param.kind_of?(Octothorpe)
 
       end
 
 
       def test_for_invalid_status(action, status)
-        raise( Pod4Error, 
-               "Invalid model status for an action of #{action}",
-               caller ) \
+        raise( Pod4Error, "Invalid model status for an action of #{action}", caller ) \
           if [:empty, :deleted].include? status
 
       end
@@ -151,18 +143,12 @@ module Pod4
 
 
       def fail_no_id_fld
-        raise POd4Error, 
-              "No ID field defined in interface",
-              caller
-
+        raise POd4Error, "No ID field defined in interface", caller
       end
 
 
       def fail_no_id
-        raise Pod4Error, 
-              "ID field missing from record",
-              caller
-
+        raise Pod4Error, "ID field missing from record", caller
       end
 
     end
@@ -170,21 +156,20 @@ module Pod4
 
 
     ##
-    # Syntactic sugar; pretty much the same as self.class.columns, which
-    # returns the `attr_columns` array.
+    # Syntactic sugar; pretty much the same as self.class.columns, which returns the `attr_columns`
+    # array.
     #
     def columns; self.class.columns.dup; end
 
 
     ##
     # Call this to write a new record to the data source.
-    # Note: create needs to set @id. But interface.create should return it, so
-    # that's okay.
+    #
+    # Note: create needs to set @id. But interface.create should return it, so that's okay.
     #
     def create
       validate
-      @model_id = interface.create(map_to_interface) \
-        unless @model_status == :error
+      @model_id = interface.create(map_to_interface) unless @model_status == :error
 
       @model_status = :okay if @model_status == :empty
       self
@@ -215,8 +200,7 @@ module Pod4
       Model.test_for_invalid_status(:update, @model_status)
 
       clear_alerts; validate 
-      interface.update(@model_id, map_to_interface) \
-        unless @model_status == :error
+      interface.update(@model_id, map_to_interface) unless @model_status == :error
 
       self
     end
@@ -241,13 +225,11 @@ module Pod4
     #
     # Override this to add validation - calling `add_alert` for each problem.
     #
-    # Note that you can only validate what is actually stored on the model. If
-    # you want to check the data being passed to the model in `set`, you need
-    # to override that routine.
+    # Note that you can only validate what is actually stored on the model. If you want to check
+    # the data being passed to the model in `set`, you need to override that routine.
     #
-    # Also, you don't have any way of telling whether you are currently
-    # creating a new record or updating an old one: override `create` and
-    # `update` respectively.
+    # Also, you don't have any way of telling whether you are currently creating a new record or
+    # updating an old one: override `create` and `update` respectively.
     #
     def validate
       # Holding pattern. All models should use super, in principal
@@ -257,13 +239,11 @@ module Pod4
     ##
     # Set instance values on the model from a Hash or Octothorpe.
     #
-    # This is what your code calls when it wants to update the model. Override
-    # it if you need it to set anything not in attr_columns, or to
-    # control data types, etc.
+    # This is what your code calls when it wants to update the model. Override it if you need it to
+    # set anything not in attr_columns, or to control data types, etc.
     #
-    # You might want to put validation here, too, if what you are validating is
-    # something that isn't actually stored on the model. You can call add_alert
-    # from here just fine.
+    # You might want to put validation here, too, if what you are validating is something that
+    # isn't actually stored on the model. You can call add_alert from here just fine.
     #
     # See also: `to_ot`, `map_to_model`, `map_to_interface`
     #
@@ -276,8 +256,7 @@ module Pod4
     ##
     # Return an Octothorpe of all the attr_columns attributes.
     #
-    # Override if you want to return any extra data. (You will need to create a
-    # new Octothorpe.) 
+    # Override if you want to return any extra data. (You will need to create a new Octothorpe.) 
     #
     # See also: `set`, `map_to_model', 'map_to_interface'
     #
@@ -289,13 +268,11 @@ module Pod4
     ##
     # Used by the interface to set the column values on the model.
     #
-    # Don't use this to set model attributes from your code; use `set`,
-    # instead.
+    # Don't use this to set model attributes from your code; use `set`, instead.
     #
-    # By default this does exactly the same as `set`. Override it if you want
-    # the model to represent data differently than the data source does --
-    # but then you will have to override `map_to_interface`, too, to convert
-    # the data back.
+    # By default this does exactly the same as `set`. Override it if you want the model to
+    # represent data differently than the data source does -- but then you will have to override
+    # `map_to_interface`, too, to convert the data back.
     #
     # See also: `to_ot`, `map_to_model'
     #
@@ -309,16 +286,15 @@ module Pod4
     ##
     # used by the model to get an OT of column values for the interface. 
     #
-    # Don't use this to get model values in your code; use `to_ot`, instead.
-    # This is called by model.create and model.update when it needs to write to
-    # the data source.
+    # Don't use this to get model values in your code; use `to_ot`, instead.# This is called by
+    # model.create and model.update when it needs to write to the data source.
     #
-    # By default this behaves exactly the same as to_ot. Override it if you
-    # want the model to represent data differently than the data source -- in
-    # which case you also need to override `map_to_model`.
+    # By default this behaves exactly the same as to_ot. Override it if you want the model to
+    # represent data differently than the data source -- in which case you also need to override
+    # `map_to_model`.
     #
-    # Bear in mind that any attribute could be nil, and likely will be when
-    # `map_to_interface` is called from the create method.
+    # Bear in mind that any attribute could be nil, and likely will be when `map_to_interface` is
+    # called from the create method.
     #
     # See also: `to_ot`, `set`.
     #
@@ -351,7 +327,6 @@ module Pod4
       end
     end
 
-
   end
   ##