A FileMaker Adapter For Feathers.js.
This is a FileMaker Adapter for feathers.js. It makes it trivial to create a feathers service for any FileMaker Layout. For non FileMaker people, a layout is a Table with a defined set of fields, and related records.
This currently passes all but two tests in the feathers-service-test suite. There is not an easy way to do a a true PUT, which would require nulling fields. When you PUT or in feathers terms 'update', you basically just get a PATCH. We also do not support the $in and $nin query filters. We may in the future. Support for $or is limited. Only single fields will work.
npm install feathers-filemaker --save
This adapter works like others Feathers Adapters. Please refer to the Feathers database adapter documentation for more details or directly at:
- Extending - How to extend a database adapter
- Pagination and Sorting - How to use pagination and sorting for the database adapter
- Querying - The common adapter querying mechanism
FileMaker Specific Configuration
This adapter takes two additional keys in it's configuration object:
connection :host : 'localhost' // server addressdb : 'Contacts'user : 'admin'pass : 'pass'
model :layout : 'Contacts' // the layout for the serviceidField : 'id' // primary key field name, defaults to 'id'
Connection specifies the host, database, user, and password to connect to the database. model specifies the layout and idField to use for the feathers service. See the complete example below for more information.
There is also an included ScriptService that will run scripts on a specified layout. That layout must be based on a dedicated TO and Table. The service creates a record in that table and dumps the data in a field before running the script. See the "Utility" Table and layout in the Test file. Add that table to your solution. The records it creates are great for logging purposes. But can be destroyed at will.
The Service will return JSON as it normally does from the last layout it is on. However if you end the script on 'Utility' layout, then it is smart enough to pull the result from the 'results' field. This lets you create custom responses with worrying about having a table to produce them from. However the "result" will be parsed as JSON so you need to make sure it is valid JSON.
This is great for running transactions scripts!
Using the Script Service
var fms = ;var script = fmsScriptService;// we configure a ScriptService, we need a connection, and a layout.app;//...// now later, anywhere we have access to the 'app' we can get the service.// assuming connection to have a db named 'Test' and our layout was 'Utility'const ScriptService = app;// and use it like this.ScriptService
var feathers = ;var fms = ;var bodyParser = ;var rest = ;var socketio = ;var mms = ;// Create a feathers instance.const app =// Enable REST services// Enable Socket.io services// Turn on JSON parser for REST services// Turn on URL-encoded parser for REST services;// create a FileMaker Service based on the Contacts Layout in the Contacts db// paginate options can also be set hereapp;// Start the server.var port = 3030;app;
EXPERIMENTAL - Use with caution.
In addition to setting up services using normal feathers idioms as described above, you can simply expose a RESTFUL endpoint to all the databases on the server. This is super simple to setup. It covers many of the common scenarios that REST is used for, however it is less powerful than normal feathers services.
The Auto Service serves a restful endpoint in the following form:
The prefix can be passed in as part of configuration. ( see below )
This will also work with WebSockets, but it's weird. And is currently doesn't have authentication. TODO:examples
Basic auth is the only option available to the Simple REST Service. JSONWeb Tokens currently won't work.
You can't use feathers hooks.
How it works
You start by creating a normal feathers server. Then setup the Simple REST Server using configure()
Note: it takes the same options as a normal Feathers-FileMaker Service, plus one more "prefix" which is where the REST API is mounted ( See above )
Connection and model are the same with a regular Service, but some of the properties aren't used or are used only as defaults
- Connection.db is ignored
- Connection.user is a default, and is overridden by basic auth
- Connection.password is a default, and is overridden by basic auth
- Model.layout is ignored.
// app.js of generated feathers appconst path = ;const serveStatic = static;const favicon = ;const compress = ;const cors = ;const feathers = ;const configuration = ;const hooks = ;const rest = ;const bodyParser = ;const socketio = ;const middleware = ;const services = ;//get SimpleRestService from feathers-filemakerconst fm = ;const SimpleRestService = fmSimpleRESTService;// you'll need a connectionconst connection =host : 'localhost'db : 'Test' // ignoreduser : 'wrong' // optional, overwritten by basic authpass : 'wrong' // optional, overwritten by basic auth;const app = ;app;appoptions'*'//configure SimpleRestService here// middleware should be last;moduleexports = app;
Copyright Todd Geist(c) 2016
Licensed under the MIT license