Siren output format

[apsoto]

I'm partial to Siren, so I would need to implement a serializer, how stable is the api for adding serializers? Do you foresee big changes still? Especially since adding Siren means adding actions ;)

[plexus]

For features that are already represented adding a serializer is very easy. For new features the first step is to see if it can be generalized across formats. We would need new syntax, and in that case I prefer to add syntax for features that are usable by more than one output format.

It seems "actions" correspond with "forms" and possibly "queries" from other formats? I have considered this case a bit but haven't come up with a definite syntax yet. Suggestions welcome.

See https://github.com/plexus/yaks/blob/master/ADDING_FORMATS.md for more info.

[plexus]

Since this thread was opened Yaks's support for "form controls" has seen a lot of love, and from what I've seen I think Siren would fit the Yaks model very well, so I'd like to add this soon. It would be an easy task, and it seems Siren is getting good traction compared to some other formats.

[DanielKuhn]

@plexus I was wondering: what's the status of Siren support? We're currently evaluating Yaks for our hypermedia API and are in favor of Siren as format.

[plexus]

Hi @DanielKuhn, I am no longer actively working on Yaks, since I don't do Ruby any more. I still review and merge pull requests, and will release a new version when there's new stuff to show. A contributed Siren serializer would be very much appreciated!