# fmrest-ruby

[![Gem Version](https://badge.fury.io/rb/fmrest.svg?style=flat)](https://rubygems.org/gems/fmrest)
![CI](https://github.com/beezwax/fmrest-ruby/workflows/CI/badge.svg)

A Ruby client for
[FileMaker 18 and 19's Data API](https://help.claris.com/en/data-api-guide)
using
[Faraday](https://github.com/lostisland/faraday) and with optional
ActiveRecord-ish ORM features through [Spyke](https://github.com/balvig/spyke).

fmrest-ruby only partially implements FileMaker 18's Data API.
See the [implementation completeness table](#api-implementation-completeness-table)
to see if a feature you need is natively supported by the gem.

## Gems

The `fmrest` gem is a wrapper for two other gems:

* `fmrest-spyke`, providing an ActiveRecord-like ORM library built on top
  of `fmrest-core` and [Spyke](https://github.com/balvig/spyke).
* `fmrest-core`, providing the core Faraday connection builder, session
  management, and other core utilities.

## Installation

Add this to your Gemfile:

```ruby
gem 'fmrest'
```

Or if you just want to use the Faraday connection without the ORM features:

```ruby
gem 'fmrest-core'
```

## Simple examples

### ORM example

Most people would want to use the ORM features:

```ruby
# A Layout model connecting to the "Honeybees Web" FileMaker layout
class Honeybee < FmRest::Layout("Honeybees Web")
  # Connection settings
  self.fmrest_config = {
    host:     "…",
    database: "…",
    username: "…",
    password: "…"
  }

  # Mapped attributes
  attributes name: "Bee Name", age: "Bee Age"

  # Portals
  has_portal :flowers

  # File container
  container :photo, field_name: "Bee Photo"
end

# Find a record by id
bee = Honeybee.find(9)

bee.name = "Hutch"

# Add a new record to portal
bee.flowers.build(name: "Daisy")

bee.save
```

### Barebones connection example (without ORM)

In case you don't need the advanced ORM features (e.g. if you only need minimal
Data API interaction and just want a lightweight solution) you can simply use
the Faraday connection provided by `fmrest-core`:

```ruby
connection = FmRest::V1.build_connection(
  host:     "…",
  database: "…",
  username: "…",
  password: "…"
)

# Get all records (as parsed JSON)
connection.get("layouts/FancyLayout/records")

# Create new record
connection.post do |req|
  req.url "layouts/FancyLayout/records"

  # You can just pass a hash for the JSON body
  req.body = { … }
end
```

See the [main document on using the base
connection](docs/BaseConnectionUsage.md) for more.

## Connection settings

The minimum required connection settings are `:host`, `:database`, `:username`
and `:password`, but fmrest-ruby has many other options you can pass when
setting up a connection (see [full list](#full-list-of-available-options) below).

`:ssl` and `:proxy` are forwarded to the underlying
[Faraday](https://github.com/lostisland/faraday) connection. You can use this
to, for instance, disable SSL verification:

```ruby
{
  host: "…",
  …
  ssl:  { verify: false }
}
```

You can also pass a `:log` option for basic request logging, see the section on
[Logging](#Logging) below.

### 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
`:account_name`     | Alias of `:username`                       | 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-and-timezones) | 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"`
`:timezone`         | The timezone for the FM server             | `:local` \| `:utc` \| `nil` | `nil`
`:autologin`        | Whether to automatically start Data API sessions | Boolean               | `true`
`:token`            | Used to manually provide a session token (e.g. if `:autologin` is `false`) | String | None

### Default connection settings

If you're only connecting to a single FM database you can configure it globally
through `FmRest.default_connection_settings=`. E.g.:

```ruby
FmRest.default_connection_settings = {
  host:     "…",
  database: "…",
  username: "…",
  password: "…"
}
```

These settings will be used by default by `FmRest::Layout` models whenever you
don't set `fmrest_config=` explicitly, as well as by
`FmRest::V1.build_connection` in case you're setting up your Faraday connection
manually.

## Session token store

fmrest-ruby includes a number of options for storing session tokens:

* Memory
* ActiveRecord
* Redis
* Moneta

See the [main document on token stores](docs/TokenStore.md) for detailed info
on how to set up each store.

## Date fields and timezones

fmrest-ruby has automatic detection and coercion of date fields to and from
Ruby date/time objects. Basic timezone support is also provided.

See the [main document on date fields](docs/DateFields.md) for more info.

## ActiveRecord-like ORM (fmrest-spyke)

[Spyke](https://github.com/balvig/spyke) is an ActiveRecord-like gem for
building REST ORM models. fmrest-ruby builds its ORM features atop Spyke,
bundled in the `fmrest-spyke` gem (already included if you're using the
`fmrest` gem).

To create a model you can inherit directly from `FmRest::Layout` (itself a
subclass of `Spyke::Base`).

```ruby
class Honeybee < FmRest::Layout
end
```

All of Spyke's basic ORM operations work as expected:

```ruby
bee = Honeybee.new

bee.name = "Hutch"
bee.save # POST request (creates new record)

bee.name = "ハッチ"
bee.save # PATCH request (updates existing record)

bee.reload # GET request

bee.destroy # DELETE request

bee = Honeybee.find(9) # GET request
```

It's recommended that you read Spyke's documentation for more information on
these basic features. If you've used ActiveRecord or similar ORM libraries
you'll find it quite familiar.

Notice that `FmRest::Layout` is aliased as `FmRest::Spyke::Base`. Previous
versions of fmrest-ruby only provided the latter version, so if you're already
using `FmRest::Spyke::Base` there's no need to rename your classes to
`FmRest::Layout`, both will continue to work interchangeably.

In addition, `FmRest::Layout` extends `Spyke::Base` with the following
features:

### FmRest::Layout.fmrest_config=

This allows you to set Data API connection settings specific to your model
class:

```ruby
class Honeybee < FmRest::Layout
  self.fmrest_config = {
    host:     "…",
    database: "…",
    username: "…",
    password: "…"
  }
end
```

This will automatically create a proper Faraday connection using those
connection settings, so you don't have to worry about setting that up.

Note that these settings are inheritable, so you could create a base class that
does the initial connection setup and then inherit from it in models using that
same connection. E.g.:

```ruby
class BeeBase < FmRest::Layout
  self.fmrest_config = { host: "…", database: "…", … }
end

class Honeybee < BeeBase
  # This model will use the same connection as BeeBase
end
```

Also, if not set, your model will try to use
`FmRest.default_connection_settings` instead.

#### Connection settings overlays

There may be cases where you want to use a different set of connection settings
depending on context. For example, if you want to use username and password
provided by the user in a web application. Since `.fmrest_config`
is set at the class level, changing the username/password for the model in one
context would also change it in all other contexts, leading to security issues.

To solve this scenario, fmrest-ruby provides a way of defining thread-local and
reversible connection settings overlays through
`.fmrest_config_overlay=`.

See the [main document on connection setting overlays](docs/ConfigOverlays.md)
for details on how it works.

### FmRest::Layout.layout

Use `layout` to set the layout name for your model.

```ruby
class Honeybee < FmRest::Layout
  layout "Honeybees Web"
end
```

Alternatively, you can set the layout name in the class definition line:

```ruby
class Honeybee < FmRest::Layout("Honeybees Web")
```

Note that you only need to manually set the layout name if the name of the
class and the name of the layout differ, otherwise fmrest-ruby will just use
the name of the class.

### FmRest::Layout.request_auth_token

Requests a Data API session token using the connection settings in
`fmrest_config` and returns it if successful, otherwise returns `false`.

You normally don't need to use this method as fmrest-ruby will automatically
request and store session tokens for you (provided that `:autologin` is
`true`).

### FmRest::Layout.logout

Use `.logout` to log out from the database session (you may call it on any
model that uses the database session you want to log out from).

```ruby
Honeybee.logout
```

### Mapped FmRest::Layout.attributes

Spyke allows you to define your model's attributes using `attributes`, however
sometimes FileMaker's field names aren't very Ruby-ORM-friendly, especially
since they may sometimes contain spaces and other special characters, so
fmrest-ruby extends `attributes`' functionality to allow you to map
Ruby-friendly attribute names to FileMaker field names. E.g.:

```ruby
class Honeybee < FmRest::Layout
  attributes first_name: "First Name", last_name: "Last Name"
end
```

You can then simply use the pretty attribute names whenever working with your
model and they will get mapped to their FileMaker fields:

```ruby
bee = Honeybee.find(1)

bee.first_name # => "Princess"
bee.last_name  # => "Buzz"

bee.first_name = "Queen"

bee.attributes # => { "First Name": "Queen", "Last Name": "Buzz" }
```

### FmRest::Layout.has_portal

You can define portal associations on your model wth `has_portal`, as such:

```ruby
class Honeybee < FmRest::Layout
  has_portal :flowers
end

class Flower < FmRest::Layout
  attributes :color, :species
end
```

See the [main document on portal associations](docs/Portals.md) for details.

### Dirty attributes

fmrest-ruby includes support for ActiveModel's Dirty mixin out of the box,
providing methods like:

```ruby
bee = Honeybee.new

bee.changed? # => false

bee.name = "Maya"

bee.changed? # => true

bee.name_changed? # => true
```

fmrest-ruby uses the Dirty functionality to only send changed attributes back
to the server on save.

You can read more about [ActiveModel's Dirty in Rails
Guides](https://guides.rubyonrails.org/active_model_basics.html#dirty).

### Query API

Since Spyke is API-agnostic it only provides a wide-purpose `.where` method for
passing arbitrary parameters to the REST backend. fmrest-ruby however is well
aware of its backend API, so it extends Spkye models with a bunch of useful
querying methods: `.query`, `.limit`, `.offset`, `.sort`, `.portal`, `.script`,
etc.

See the [main document on querying](docs/Querying.md) for detailed information
on the query API methods.

### Finding records in batches

Sometimes you want to iterate over a very large number of records to do some
processing, but requesting them all at once would result in one huge request to
the Data API, and loading too many records in memory all at once.

To mitigate this problem you can use `.find_in_batches` and `.find_each`.

See the [main document on finding in batches](docs/FindInBatches.md) for
detailed information on how those work.

### Container fields

You can define container fields on your model class with `container`:

```ruby
class Honeybee < FmRest::Layout
  container :photo, field_name: "Beehive Photo ID"
end
```

See the [main document on container fields](docs/ContainerFields.md) for
details on how to use it.

### Script execution

The FM Data API allows running scripts as part of many types of requests, and
`fmrest-spyke` provides mechanisms for all of them.

See the [main document on script execution](docs/ScriptExecution.md) for
details.

### Setting global field values

You can call `.set_globals` on any `FmRest::Layout` model to set global
field values on the database that model is configured for.

See the [main document on setting global field values](docs/GlobalFields.md)
for details.

## Logging

If using `fmrest-spyke` with Rails then pretty log output will be set up for
you automatically by Spyke (see [their
README](https://github.com/balvig/spyke#log-output)).

You can also enable simple Faraday STDOUT logging of raw requests (useful for
debugging) by passing `log: true` in the options hash for either
`FmRest.default_connection_settings=` or your models' `fmrest_config=`, e.g.:

```ruby
FmRest.default_connection_settings = {
  host: "…",
  …
  log:  true
}

# Or in your model
class LoggyBee < FmRest::Layout
  self.fmrest_config = {
    host: "…",
    …
    log:  true
  }
end
```

If you need to set up more complex logging for your models can use the
`faraday` block inside your class to inject your own logger middleware into the
Faraday connection, e.g.:

```ruby
class LoggyBee < FmRest::Layout
  faraday do |conn|
    conn.response :logger, MyApp.logger, bodies: true
  end
end
```

## API implementation completeness table

FM Data API reference: https://fmhelp.filemaker.com/docs/18/en/dataapi/

| FM 18 Data API feature              | Supported by basic connection | Supported by FmRest::Layout |
|-------------------------------------|-------------------------------|-----------------------------|
| Log in using HTTP Basic Auth        | Yes                           | Yes                         |
| 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                         |
| Get product information             | Manual*                       | No                          |
| Get database names                  | Manual*                       | No                          |
| Get script names                    | Manual*                       | No                          |
| Get layout names                    | Manual*                       | No                          |
| Get layout metadata                 | Manual*                       | No                          |
| Create a record                     | Manual*                       | Yes                         |
| Edit a record                       | Manual*                       | Yes                         |
| Duplicate a record                  | Manual*                       | No                          |
| Delete a record                     | Manual*                       | Yes                         |
| Edit portal records                 | Manual*                       | Yes                         |
| Get a single record                 | Manual*                       | Yes                         |
| Get a range of records              | Manual*                       | Yes                         |
| Get container data                  | Manual*                       | Yes                         |
| Upload container data               | Manual*                       | Yes                         |
| Perform a find request              | Manual*                       | Yes                         |
| Set global field values             | Manual*                       | Yes                         |
| Run a script                        | Manual*                       | Yes                         |
| Run a script with another request   | Manual*                       | Yes                         |

\* You can manually supply the URL and JSON to a `FmRest` connection.

## Supported Ruby versions

fmrest-ruby aims to support and is [tested against](https://github.com/beezwax/fmrest-ruby/actions?query=workflow%3ACI)
the following Ruby implementations:

* Ruby 2.5
* Ruby 2.6
* Ruby 2.7
* Ruby 3.0

## Gem development

After checking out the repo, run `bin/setup` to install dependencies. Then, run
`rake spec` to run the tests. You can also run `bin/console` for an interactive
prompt that will allow you to experiment (it will auto-load all fixtures in
spec/fixtures).

To install all gems onto your local machine, run
`bundle exec rake all:install`. To release a new version, update the version
number in `lib/fmrest/version.rb`, and then run `bundle exec rake all:release`,
which will create a git tag for the version, push git commits and tags, and
push the `.gem` files to [rubygems.org](https://rubygems.org).

## 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.