Add 'links' support

[mrichar1]

Hi,

Have found this library really useful! I'm currently looking to test the top-level links element of jsonapi in code, and there doesn't seem to be a way to add links to the fake server data - in particular self, containing the url of the fetched object.

Would it be possible to add this? Thanks!

[mblackritter]

Hi @mrichar1,

First, please let me send you a few cheers and congrats for your *JSONAPI Vuex package! 🥳🥰

I'm currently using it and by that also found this brilliantly simple to handle Fake *JSONAPI Server (Cheers @dbrekalo, join us for the party 🍻), which I now also use as my mocking solution and replaced *JSONAPI Server, which works great, but provides a whole server/backend solution, which is unneccessary overhead for simple mocking. And yeah, same as you, I also tried *JSONAPI Mock before, but that turned out rather cumbersome.

Second, as the glorious Fake *JSONAPI Server pushes out the resources "as is", you can just add anything in your resource object and it'll show up in the response. 🤩

* I generally tend to write JSONAPI, to make it distinkt from all that "something JSON API" out there.

{
  "widget": {
    "data": [
      {
        "type": "widget",
        "id": "11",
        "attributes": {
          "name": "sprocket",
          "color": "black"
        },
        "links": { // This just works
          "self": "http://localhost:9010/widget/11"
        }
      }
    ]
  }
}

I would suggest to dynamically generate the resource object, so you have automatic link generation.

Cheers,
Black

PS: 2019 seems to be JSONAPI's big showtime, finally! 😹💦

[mrichar1]

Ah - kicking myself now that I didn't notice that workaround!

I still think it would be better overall to have links generated by fake-json-api-server, since it is in control of running the webserver part, so has a better idea of its urls etc - but this is an easy fix in the short term to let me keep testing things.

[mblackritter]

Not sure if it's a workaround or just how Fake JSONAPI Server works. Guess there's a reason for the "Fake" in its name. 😌 Compared to other solutions, it's quite static and practically doesn't do much more than populating "included", as far as I could see. It also doesn't give the option to include resource types, it just includes everything by default, which is okay for my use-case, because at first I was concerned that it wouldn't provide includes at all.

Maybe you should've a look at JSONAPI Server which does links and a lot more, including sort and filter out of the box, even like bookings?filter[attendees]=>5 (Bigger than 5).

Or check out the big gun like Fortune.js with Fortune-JSON-API, which seems to be able to even store data permanently using Fortune-FS. Fortune.js itself can also run in the browser, just like Fake JSONAPI Server, but I'm not sure if Fortune-JSON-API can.

Technically, Fortune.js seems like the most viable solution for whatever one might throw at it, but seemed overkill for my limited use case, as the final backend is also within my scope.

Looking at the tests, it might not provide for advanced filter rules by default, but overall it looks the most promising and extendable.

Should we both find the thrill to rock this, we might setup a ready-to-go repo for Fortune.js as a JSONAPI mock.

But how to call it? The most obvious names are taken. What about "Fake JSONAPI Mock"? löl 😹💦

Cheers,
Black