fms
![Build Status](https://travis-ci.org/f/f.png?branch=master)
A FileMaker Adapter For Feathers.js.
About
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.
Install
npm install feathers-filemaker --save
Documentation
This adapter works like others Feathers Adapters. Please refer to the Feathers database adapter documentation for more details or directly at:
FileMaker Specific Configuration
This adapter takes two additional keys in it's configuration object: connection
and model
Connection
connection :{
host : 'localhost',
db : 'Contacts'
user : 'admin'
pass : 'pass'
}
Model
model :{
layout : 'Contacts'
idField : '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.
Script Service
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 = require('feathers-filemaker');
var script = fms.ScriptService;
app.configure(script({connection, layout: 'Utility'}));
const ScriptService = app.service('fms-script-service');
ScriptService.run('ScriptName' , {any:'data', I: 'want'} ).then(handleResults)
Complete Example
var feathers = require('feathers');
var bodyParser = require('body-parser');
var rest = require('feathers-rest');
var socketio = require('feathers-socketio');
var mms = require('feathers-memory');
const app = feathers()
.configure(rest())
.configure(socketio())
.use(bodyParser.json())
.use(bodyParser.urlencoded({ extended: true }));
app.use('/contacts', fms({
connection :{
host : 'localhost',
db : 'Contacts'
user : 'admin'
pass : 'pass'
},
model :{
layout : 'Contacts'
idField : 'id'
},
paginate: {
default: 2,
max: 4
}
}));
var port = 3030;
app.listen(port, function() {
console.log(`Feathers server listening on port ${port}`);
});
License
Copyright Todd Geist(c) 2016
Licensed under the MIT license