fmrest 0.6.0 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 185e6173a3f500ea6fc8ad40df8f52ba538fdd8e3545537e947f19bfd79a3124
-  data.tar.gz: 89f5c6774366599e1baeef57662af77a3ceb5174abd58e6fd562c2aa29b85384
+  metadata.gz: ab46f70bffcfea32ef2bfd5021f03fa654bb43134e22b8e22a20d9955afe9caf
+  data.tar.gz: 32ce4378ff291d2c41d9b255b032d4562d7544a477765748c87c49a655449405
 SHA512:
-  metadata.gz: b7aa56e455da60fe7b571e2ce4d70ae118ca7ade57356cbdade2b0679f66d10e9d689a4bc3af5ddfb06dfc6d7395af35b0518c23077dbfb28a9e395b845e0841
-  data.tar.gz: c764ee1dc1962b3f6264ed6a4f26f0b88dd5c69cb62bca93dd269398c3e0d350ced4177b2842ce24136d7d0b84cb9a4809ce23ca1965b923fb91fc7b37ae39e1
+  metadata.gz: a68af2d8e53631b1d5c4d9e5e0849d224ff3918d1138d437463e30318ae81c36ca968d226f2f3631dbaa0d21b6287c1899e3b322a716729ad0d8b77aff80fd8d
+  data.tar.gz: ace50f913960e6b2edd190c8c1cbb75a0ebf15c0c3f0e8343720155f1c53b78bb9fd942be0a5e9bf2a2bc1ff729277f86360ffa4bba397ba48abe86c07db02ad

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## Changelog
 
+### 0.7.0
+
+* Added date coercion feature
+
 ### 0.6.0
 
 * Implemented session logout

data/README.md

@@ -105,6 +105,22 @@ You can also pass a `:log` option for basic request logging, see the section on
 `:username` is also aliased as `:account_name` to provide cross-compatibility
 with the ginjo-rfm gem.
 
+### Full list of available options
+
+Option              | Description                                | Format                      | Default
+--------------------|--------------------------------------------|-----------------------------|--------
+`:host`             | Hostname with optional port, e.g. `"example.com:9000"` | String          | None
+`:database`         |                                            | String                      | None
+`:username`         |                                            | String                      | None
+`:password`         |                                            | String                      | None
+`:ssl`              | SSL options to be forwarded to Faraday     | Faraday SSL options         | None
+`:proxy`            | Proxy options to be forwarded to Faraday   | Faraday proxy options       | None
+`:log`              | Log JSON responses to STDOUT               | Boolean                     | `false`
+`:coerce_dates`     | See section on [date fields](#date-fields) | Boolean \| `:hybrid` \| `:full` | `false`
+`:date_format`      | Date parsing format                        | String (FM date format)     | `"MM/dd/yyyy"`
+`:timestamp_format` | Timestmap parsing format                   | String (FM date format)     | `"MM/dd/yyyy HH:mm:ss"`
+`:time_format`      | Time parsing format                        | String (FM date format)     | `"HH:mm:ss"`
+
 ### Default connection settings
 
 If you're only connecting to a single FM database you can configure it globally
@@ -122,6 +138,7 @@ FmRest.default_connection_settings = {
 This configuration will be used by default by `FmRest::V1.build_connection` as
 well as your models whenever you don't pass a configuration hash explicitly.
 
+
 ## Session token store
 
 By default fmrest-ruby will use a memory-based store for the session tokens.
@@ -218,6 +235,54 @@ FmRest.token_store = FmRest::TokenStore::Moneta.new(
 **NOTE:** the moneta gem is not included as a dependency of fmrest-ruby, so
 you'll have to add it to your Gemfile.
 
+
+## Date fields
+
+Since the Data API uses JSON (wich doesn't provide a native date/time object),
+dates and timestamps are received in string format. By default fmrest-ruby
+leaves those string fields untouched, but it provides an opt-in feature to try
+to automatically "coerce" them into Ruby date objects.
+
+The connection option `:coerce_dates` controls this feature. Possible values
+are:
+
+* `:full`: whenever a string matches the given date/timestamp/time format,
+  convert them to `Date` or `DateTime` objects as appropriate
+* `:hybrid` or `true`: similar as above, but instead of converting to regular
+  `Date`/`DateTime` it converts strings to `FmRest::StringDate` and
+  `FmRest::StringDateTime`, "hybrid" classes provided by fmrest-ruby that
+  retain the functionality of `String` while also providing most the
+  functionality of `Date`/`DateTime` (more on this below)
+* `false`: disable date coercion entirely (default), leave original string
+  values untouched
+
+Enabling date coercion works with both basic fmrest-ruby connections and Spyke
+models (ORM).
+
+The connection options `:date_format`, `:timestamp_format` and `:time_format`
+control how to match and parse dates. You only need to provide these if you use
+a date/time localization different from American format (the default).
+
+Future versions of fmrest-ruby will provide better (and less heuristic) ways of
+specifying and/or detecting date fields (e.g. by requesting layout metadata or
+a DSL in model classes).
+
+### Hybrid string/date objects
+
+`FmRest::StringDate` and `FmRest::StringDateTime` are special classes that
+inherit from `String`, but internally parse and store a `Date`/`DateTime`
+(respectively), and delegate any methods not provided by `String` to those
+objects. In other words, they quack like a duck *and* bark like a dog.
+
+You can use these when you want fmrest-ruby to provide you with date objects,
+but you don't want to worry about date coercion of false positives (i.e. a
+string field that gets converted to `Date` because it just so matched the given
+date format).
+
+Be warned however that these classes come with a fair share of known gotchas
+(see GitHub wiki for more info).
+
+
 ## Spyke support (ActiveRecord-like ORM)
 
 [Spyke](https://github.com/balvig/spyke) is an ActiveRecord-like gem for
@@ -830,6 +895,7 @@ same metadata hash with script execution results. Note that this does not apply
 to retrieving single records, in that case you'll have to use
 `.last_request_metadata`.
 
+
 ## Logging
 
 If using fmrest-ruby + Spyke in a Rails app pretty log output will be set up
@@ -883,7 +949,7 @@ FM Data API reference: https://fmhelp.filemaker.com/docs/18/en/dataapi/
 | Log in using OAuth                  | No                            | No                               |
 | Log in to an external data source   | No                            | No                               |
 | Log in using a FileMaker ID account | No                            | No                               |
-| Log out                             | Yes                           | Yes
+| Log out                             | Yes                           | Yes                              |
 | Get product information             | Manual*                       | No                               |
 | Get database names                  | Manual*                       | No                               |
 | Get script names                    | Manual*                       | No                               |
@@ -904,19 +970,6 @@ FM Data API reference: https://fmhelp.filemaker.com/docs/18/en/dataapi/
 
 \* You can manually supply the URL and JSON to a `FmRest` connection.
 
-## TODO
-
-- [ ] Support for FM18 features
-- [ ] Better/simpler-to-use core Ruby API
-- [ ] Better API documentation and README
-- [ ] Oauth support
-- [x] Support for portal limit and offset
-- [x] More options for token storage
-- [x] Support for container fields
-- [x] Optional logging
-- [x] FmRest::Spyke::Base class for single inheritance (as alternative for mixin)
-- [x] Specs
-- [x] Support for portal data
 
 ## Gem development
 
@@ -931,6 +984,7 @@ release a new version, update the version number in `version.rb`, and then run
 git commits and tags, and push the `.gem` file to
 [rubygems.org](https://rubygems.org).
 
+
 ## Contributing
 
 Bug reports and pull requests are welcome. This project is intended to be a
@@ -938,20 +992,16 @@ safe, welcoming space for collaboration, and contributors are expected to
 adhere to the [Contributor Covenant](http://contributor-covenant.org) code of
 conduct.
 
+
 ## License
 
 The gem is available as open source under the terms of the
 [MIT License](https://opensource.org/licenses/MIT).
 See [LICENSE.txt](LICENSE.txt).
 
+
 ## Disclaimer
 
 This project is not sponsored by or otherwise affiliated with FileMaker, Inc,
 an Apple subsidiary. FileMaker is a trademark of FileMaker, Inc., registered in
 the U.S. and other countries.
-
-## Code of Conduct
-
-Everyone interacting in the fmrest-ruby project’s codebases, issue trackers,
-chat rooms and mailing lists is expected to follow the [code of
-conduct](CODE_OF_CONDUCT.md).

data/lib/fmrest/spyke.rb

@@ -8,7 +8,7 @@ rescue LoadError => e
 end
 
 require "fmrest"
-require "fmrest/spyke/json_parser"
+require "fmrest/spyke/spyke_formatter"
 require "fmrest/spyke/model"
 require "fmrest/spyke/base"
 

data/lib/fmrest/spyke/model/associations.rb

@@ -10,7 +10,7 @@ module FmRest
 
         included do
           # Keep track of portal options by their FM keys as we could need it
-          # to parse the portalData JSON in JsonParser
+          # to parse the portalData JSON in SpykeFormatter
           class_attribute :portal_options, instance_accessor: false, instance_predicate: false
 
           # class_attribute supports a :default option since ActiveSupport 5.2,
@@ -37,7 +37,7 @@ module FmRest
           def has_portal(name, options = {})
             create_association(name, Portal, options)
 
-            # Store options for JsonParser to use if needed
+            # Store options for SpykeFormatter to use if needed
             portal_key = options[:portal_key] || name
             self.portal_options = portal_options.merge(portal_key.to_s => options.dup.merge(name: name.to_s)).freeze
 

data/lib/fmrest/spyke/model/connection.rb

@@ -38,15 +38,25 @@ module FmRest
           private
 
           def fmrest_connection
-            @fmrest_connection ||= FmRest::V1.build_connection(fmrest_config || FmRest.default_connection_settings) do |conn|
-              faraday_block.call(conn) if faraday_block
-
-              # Pass the class to JsonParser's initializer so it can have
-              # access to extra context defined in the model, e.g. a portal
-              # where name of the portal and the attributes prefix don't match
-              # and need to be specified as options to `portal`
-              conn.use FmRest::Spyke::JsonParser, self
-            end
+            @fmrest_connection ||=
+              begin
+                config = fmrest_config || FmRest.default_connection_settings
+
+                FmRest::V1.build_connection(config) do |conn|
+                  faraday_block.call(conn) if faraday_block
+
+                  # Pass the class to SpykeFormatter's initializer so it can have
+                  # access to extra context defined in the model, e.g. a portal
+                  # where name of the portal and the attributes prefix don't match
+                  # and need to be specified as options to `portal`
+                  conn.use FmRest::Spyke::SpykeFormatter, self
+
+                  conn.use FmRest::V1::TypeCoercer, config
+
+                  # FmRest::Spyke::JsonParse expects symbol keys
+                  conn.response :json, parser_options: { symbolize_names: true }
+                end
+              end
           end
         end
       end

data/lib/fmrest/spyke/{json_parser.rb → spyke_formatter.rb}

@@ -6,7 +6,7 @@ module FmRest
   module Spyke
     # Response Faraday middleware for converting FM API's response JSON into
     # Spyke's expected format
-    class JsonParser < ::Faraday::Response::Middleware
+    class SpykeFormatter < ::Faraday::Response::Middleware
       SINGLE_RECORD_RE = %r(/records/\d+\z).freeze
       MULTIPLE_RECORDS_RE = %r(/records\z).freeze
       CONTAINER_RE = %r(/records/\d+/containers/[^/]+/\d+\z).freeze
@@ -24,7 +24,9 @@ module FmRest
 
       # @param env [Faraday::Env]
       def on_complete(env)
-        json = parse_json(env.body)
+        return unless env.body.is_a?(Hash)
+
+        json = env.body
 
         case
         when single_record_request?(env)
@@ -229,12 +231,6 @@ module FmRest
       def execute_script_request?(env)
         env.method == :get && env.url.path.match(SCRIPT_REQUEST_RE)
       end
-
-      # @param source [String] a JSON string
-      # @return [Hash] the parsed JSON
-      def parse_json(source)
-        JSON.parse(source, symbolize_names: true)
-      end
     end
   end
 end

data/lib/fmrest/string_date.rb

@@ -0,0 +1,181 @@
+# frozen_string_literal: true
+
+require "date"
+
+module FmRest
+  # Gotchas:
+  #
+  # 1.
+  #
+  #   Date === <StringDate instance> # => false
+  #
+  # The above can affect case conditions, as trying to match a StringDate
+  # with:
+  #
+  #   case obj
+  #   when Date
+  #     ...
+  #
+  # ...will not work.
+  #
+  # Instead one must specify the FmRest::StringDate class:
+  #
+  #   case obj
+  #   when Date, FmRest::StringDate
+  #     ...
+  #
+  # 2.
+  #
+  # StringDate#eql? only matches other strings, not dates.
+  #
+  # This could affect hash indexing when a StringDate is used as a key.
+  #
+  # TODO: Verify the above
+  #
+  # 3.
+  #
+  # StringDate#succ and StringDate#next return a String, despite Date#succ
+  # and Date#next also existing.
+  #
+  # Workaround: Use StringDate#next_day or strdate + 1
+  #
+  # 4.
+  #
+  # StringDate#to_s returns the original string, not the Date string
+  # representation.
+  #
+  # Workaround: Use strdate.to_date.to_s
+  #
+  # 5.
+  #
+  # StringDate#hash returns the hash for the string (important when using
+  # a StringDate as a hash key)
+  #
+  # 6.
+  #
+  # StringDate#as_json returns the string
+  #
+  # Workaround: Use strdate.to_date.as_json
+  #
+  # 7.
+  #
+  # Equality with Date is not reciprocal:
+  #
+  #   str_date == date #=> true
+  #   date == str_date #=> false
+  #
+  # NOTE: Potential workaround: Inherit StringDate from Date instead of String
+  #
+  # 8.
+  #
+  # Calling string transforming methods (e.g. .upcase) returns a StringDate
+  # instead of a String.
+  #
+  # NOTE: Potential workaround: Inherit StringDate from Date instead of String
+  #
+  class StringDate < String
+    DELEGATE_CLASS = ::Date
+
+    class InvalidDate < ArgumentError; end
+
+    class << self
+      alias_method :strptime, :new
+    end
+
+    def initialize(str, date_format, **str_args)
+      super(str, **str_args)
+
+      begin
+        @delegate = self.class::DELEGATE_CLASS.strptime(str, date_format)
+      rescue ArgumentError
+        raise InvalidDate
+      end
+
+      freeze
+    end
+
+    def is_a?(klass)
+      klass == ::Date || super
+    end
+    alias_method :kind_of?, :is_a?
+
+    def to_date
+      @delegate
+    end
+
+    def to_datetime
+      @delegate.to_datetime
+    end
+
+    def to_time
+      @delegate.to_time
+    end
+
+    # ActiveSupport method
+    def in_time_zone(*_)
+      @delegate.in_time_zone(*_)
+    end
+
+    def inspect
+      "#<#{self.class.name} #{@delegate.inspect} - #{super}>"
+    end
+
+    def <=>(oth)
+      return @delegate <=> oth if oth.is_a?(::Date) || oth.is_a?(Numeric)
+      super
+    end
+
+    def +(val)
+      return @delegate + val if val.kind_of?(Numeric)
+      super
+    end
+
+    def <<(val)
+      return @delegate << val if val.kind_of?(Numeric)
+      super
+    end
+
+    def ==(oth)
+      return @delegate == oth if oth.kind_of?(::Date) || oth.kind_of?(Numeric)
+      super
+    end
+    alias_method :===, :==
+
+    def upto(oth, &blk)
+      return @delegate.upto(oth, &blk) if oth.kind_of?(::Date) || oth.kind_of?(Numeric)
+      super
+    end
+
+    def between?(a, b)
+      return @delegate.between?(a, b) if [a, b].any? {|o| o.is_a?(::Date) || o.is_a?(Numeric) }
+      super
+    end
+
+    private
+
+    def respond_to_missing?(name, include_private = false)
+      @delegate.respond_to?(name, include_private)
+    end
+
+    def method_missing(method, *args, &block)
+      @delegate.send(method, *args, &block)
+    end
+  end
+
+  class StringDateTime < StringDate
+    DELEGATE_CLASS = ::DateTime
+
+    def is_a?(klass)
+      klass == ::DateTime || super
+    end
+    alias_method :kind_of?, :is_a?
+
+    def to_date
+      @delegate.to_date
+    end
+
+    def to_datetime
+      @delegate
+    end
+  end
+end

data/lib/fmrest/v1.rb

@@ -7,6 +7,10 @@ require "fmrest/v1/utils"
 
 module FmRest
   module V1
+    DEFAULT_DATE_FORMAT = "MM/dd/yyyy"
+    DEFAULT_TIME_FORMAT = "HH:mm:ss"
+    DEFAULT_TIMESTAMP_FORMAT = "#{DEFAULT_DATE_FORMAT} #{DEFAULT_TIME_FORMAT}"
+
     extend Connection
     extend Paths
     extend ContainerFields

data/lib/fmrest/v1/connection.rb

@@ -5,7 +5,7 @@ require "uri"
 module FmRest
   module V1
     module Connection
-      BASE_PATH = "/fmi/data/v1/databases".freeze
+      BASE_PATH = "/fmi/data/v1/databases"
 
       # Builds a complete DAPI Faraday connection with middleware already
       # configured to handle authentication, JSON parsing, logging and DAPI
@@ -19,7 +19,6 @@ module FmRest
       # @option (see #base_connection)
       # @return (see #base_connection)
       def build_connection(options = FmRest.default_connection_settings, &block)
-
         base_connection(options) do |conn|
           conn.use RaiseErrors
           conn.use TokenSession, options
@@ -38,8 +37,9 @@ module FmRest
 
           # Allow overriding the default response middleware
           if block_given?
-            yield conn
+            yield conn, options
           else
+            conn.use TypeCoercer, options
             conn.response :json
           end
 
@@ -86,3 +86,4 @@ end
 
 require "fmrest/v1/token_session"
 require "fmrest/v1/raise_errors"
+require "fmrest/v1/type_coercer"

data/lib/fmrest/v1/token_session.rb

@@ -14,6 +14,8 @@ module FmRest
       TOKEN_STORE_INTERFACE = [:load, :store, :delete].freeze
       LOGOUT_PATH_MATCHER = %r{\A(#{FmRest::V1::Connection::BASE_PATH}/[^/]+/sessions/)[^/]+\Z}.freeze
 
+      # @param app [#call]
+      # @param options [Hash]
       def initialize(app, options = FmRest.default_connection_settings)
         super(app)
         @options = options

data/lib/fmrest/v1/type_coercer.rb

@@ -0,0 +1,117 @@
+# frozen_string_literal: true
+
+require "fmrest/string_date"
+
+module FmRest
+  module V1
+    class TypeCoercer < Faraday::Response::Middleware
+      # We use this date to represent a time for consistency with ginjo-rfm
+      JULIAN_ZERO_DAY = "-4712/1/1"
+
+      COERCE_HYBRID = [:hybrid, "hybrid", true].freeze
+      COERCE_FULL = [:full, "full"].freeze
+
+      # @param app [#call]
+      # @param options [Hash]
+      def initialize(app, options = FmRest.default_connection_settings)
+        super(app)
+        @options = options
+      end
+
+      def on_complete(env)
+        return unless enabled?
+        return unless env.body.kind_of?(Hash)
+
+        data = env.body.dig("response", "data") || env.body.dig(:response, :data)
+
+        return unless data
+
+        data.each do |record|
+          field_data = record["fieldData"] || record[:fieldData]
+          portal_data = record["portalData"] || record[:portalData]
+
+          # Build an enumerator that iterates over hashes of fields
+          enum = Enumerator.new { |y| y << field_data }
+          if portal_data
+            portal_data.each_value do |portal_records|
+              enum += portal_records.to_enum
+            end
+          end
+
+          enum.each { |hash| coerce_fields(hash) }
+        end
+      end
+
+      private
+
+      def coerce_fields(hash)
+        hash.each do |k, v|
+          next unless v.is_a?(String)
+          next if k == "recordId" || k == :recordId || k == "modId" || k == :modId
+
+          begin
+            str_timestamp = datetime_class.strptime(v, datetime_format)
+            hash[k] = str_timestamp
+            next
+          rescue ArgumentError
+          end
+
+          begin
+            str_date = date_class.strptime(v, date_format)
+            hash[k] = str_date
+            next
+          rescue ArgumentError
+          end
+
+          begin
+            str_time = datetime_class.strptime("#{JULIAN_ZERO_DAY} #{v}", time_format)
+            hash[k] = str_time
+            next
+          rescue ArgumentError
+          end
+        end
+      end
+
+      def date_class
+        @date_class ||=
+          case coerce_dates
+          when *COERCE_HYBRID
+            StringDate
+          when *COERCE_FULL
+            Date
+          end
+      end
+
+      def datetime_class
+        @datetime_class ||=
+          case coerce_dates
+          when *COERCE_HYBRID
+            StringDateTime
+          when *COERCE_FULL
+            DateTime
+          end
+      end
+
+      def date_format
+        @date_format ||=
+          FmRest::V1.convert_date_time_format(@options[:date_format] || DEFAULT_DATE_FORMAT)
+      end
+
+      def datetime_format
+        @datetime_format ||=
+          FmRest::V1.convert_date_time_format(@options[:timestamp_format] || DEFAULT_TIMESTAMP_FORMAT)
+      end
+
+      def time_format
+        @time_format ||=
+          "%Y/%m/%d " + FmRest::V1.convert_date_time_format(@options[:time_format] || DEFAULT_TIME_FORMAT)
+      end
+
+      def coerce_dates
+        @options.fetch(:coerce_dates, false)
+      end
+
+      alias_method :enabled?, :coerce_dates
+    end
+  end
+end

data/lib/fmrest/v1/utils.rb

@@ -5,6 +5,17 @@ module FmRest
     module Utils
       VALID_SCRIPT_KEYS = [:prerequest, :presort, :after].freeze
 
+      FM_DATETIME_FORMAT_MATCHER = /MM|mm|dd|HH|ss|yyyy/.freeze
+
+      FM_DATETIME_FORMAT_SUBSTITUTIONS = {
+        "MM"   => "%m",
+        "dd"   => "%d",
+        "yyyy" => "%Y",
+        "HH"   => "%H",
+        "mm"   => "%M",
+        "ss"   => "%S"
+      }.freeze
+
       # Converts custom script options to a hash with the Data API's expected
       # JSON script format.
       #
@@ -72,6 +83,12 @@ module FmRest
         params
       end
 
+      # Converts a FM date-time format to `Date.strptime` format
+      #
+      def convert_date_time_format(fm_format)
+        fm_format.gsub(FM_DATETIME_FORMAT_MATCHER, FM_DATETIME_FORMAT_SUBSTITUTIONS)
+      end
+
       private
 
       def convert_script_arguments(script_arguments, suffix = nil)

data/lib/fmrest/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module FmRest
-  VERSION = "0.6.0"
+  VERSION = "0.7.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fmrest
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.7.0
 platform: ruby
 authors:
 - Pedro Carbajal
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-05-05 00:00:00.000000000 Z
+date: 2020-05-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday
@@ -231,7 +231,6 @@ files:
 - ".travis.yml"
 - ".yardopts"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -242,7 +241,6 @@ files:
 - lib/fmrest/spyke.rb
 - lib/fmrest/spyke/base.rb
 - lib/fmrest/spyke/container_field.rb
-- lib/fmrest/spyke/json_parser.rb
 - lib/fmrest/spyke/model.rb
 - lib/fmrest/spyke/model/associations.rb
 - lib/fmrest/spyke/model/attributes.rb
@@ -255,7 +253,9 @@ files:
 - lib/fmrest/spyke/model/uri.rb
 - lib/fmrest/spyke/portal.rb
 - lib/fmrest/spyke/relation.rb
+- lib/fmrest/spyke/spyke_formatter.rb
 - lib/fmrest/spyke/validation_error.rb
+- lib/fmrest/string_date.rb
 - lib/fmrest/token_store.rb
 - lib/fmrest/token_store/active_record.rb
 - lib/fmrest/token_store/base.rb
@@ -270,6 +270,7 @@ files:
 - lib/fmrest/v1/token_session.rb
 - lib/fmrest/v1/token_store/active_record.rb
 - lib/fmrest/v1/token_store/memory.rb
+- lib/fmrest/v1/type_coercer.rb
 - lib/fmrest/v1/utils.rb
 - lib/fmrest/version.rb
 homepage: https://github.com/beezwax/fmrest-ruby

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at pedro_c@beezwax.net. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/