fortunejs / fortune-micro-api Goto Github PK

I'm curious if it's possible to have fortune-micro-api work with Swagger.

I saw these
https://github.com/swagger-api/swagger-node/tree/master/project-skeletons

But not sure if it would apply?

Thanks in advance!

When using fields it also hides the links. This should not be the case.

Problem here:

It should iterate over all of the fields in the record type definition.

Support custom namespaces. This will require some changes upstream in Fortune to allow meta-information on record types.

Hi,

I've started some work on a potential "fortune-stardog" or "fortune-sparql" module, to try to link the fortune-micro-api to an RDF triple store by modifying the fortune-nedb module, starting with "create (type, records)"

I'm a ways off, but curious around the approach I'm taking since JSON-LD inbound are flattened triples if perhaps rather than converting from JSON-LD to an intermediary type & records. Instead grab the json and use the node json-ld library to manipulate it for the triple store?

This is what I started with and would like to instead have a fortune-micro-api in front of it so it would be JSON-LD from the restful service inbound as well as outbound :
https://github.com/Complexible/stardog.js/tree/develop/examples/express-app

Any feedback appreciated!

The latest published version 2016-09-06 has some additions:

• Entry point now includes vocabulary.
• @vocab property must be path to API suffixed with #.
• Optional application/x-micro-api media type based on MessagePack.

I think that this would benefit from an adapter implementation.

var microApiAdapter = require('fortune-micro-api/adapter')

Related to fortunejs/fortune#261

Babel considered harmful.

I apologize if I am missing something obvious, but I cannot get the "field" query parameter to work. In my case I have a user record type with a name and an age, and I want to show the name only. I have tried writing the query string in all kinds of formats, including "?field[name]" and "?fields[name]", but nothing happens and the meta object just says "µ:meta":{ ... "field":{} }".

I'd be grateful if you could give me an example on how to use the "fields" parameter correctly!

I happened upon another issue while trying to find the correct format for the query string. The following URL gave an unexpected result:

/users?limit=1&sort=-age&fields[age]

When making a GET request to the above URL, the meta object returned this "µ:meta":{ ... "field":{}, "sort":{"age&fields[age]":false} }".

Suppose I want to use schema.org context, and I have a type definition:

store.defineType('product', {...})

The value of @type has to be Product with a capital first letter.

This would reduce the maintenance burden on this repository by removing a lot of duplicate code.