Expected Behavior

Fix this error: Another definition with same name exis

Great stuff! I'm planning to use API for my dashboard Pandemic Estimator but I wish your API had a better documentation on methodology. I'm using JHU directly and I know what chaos it is, the most blatant example being that they provide "cumulative data" that's not cumulative quite often in practice. And the whole change of file formats, etc.

Can you please de

https://github.com/daptin/daptin/blob/aa77b35feeb48557b42a13b7a05fb291eb1e562a/docs_markdown/docs/features/enable-data-auditing.md#L1

This issue was generated by todo based on a todo comment in aa77b35feeb48557b42a13b7a05fb291eb1e562a. It's been assigned to @artpar because they committed the code.

Usage documentation and the example app are not consistent with each other. There are several classes used in the example that lack proper usage documentation and docstrings.

Documentation updates (or changes to use documented classes and deprecation of undocumented classes) are needed for the following:

• `re

Expected Behavior

Swagger (JSON-API) allows attributes and relationships to have user defined descriptions added to the documentation through the ApiModelProperty annotation.

GraphQL should support a similar mechanism.

Current Behavior

The description for attributes is left blank.

Possible Solution

Create a new Elide annotation that adds descriptions (and other attributes in A

If you PATCHed to /posts/1, but send payload with a different id:

{
  data: {
    id: 789,
    type: 'posts',
    attributes: { ... }
  }
}

We pay attention to the payload and not the URL - instead let's throw an error when there is a mismatch.

The serialization docs say the following:

ref: If present, it's considered as a relationships.
id: Configurable identifier field for the resource. Default: id.

I don't understand what one is doing over the other? What if I specify a ref but no id, and there is no id field?

Happy to contribute to clarify docs once I understand the difference.

Thanks.

Currently the module field on package.json points to src/simpla.js but really it should point to a separate build, that's been transpiled, but not bundled. This means that whatever module bundling system consumers are using will still be used, but it won't need to be transpiled. As it currently stands, users can come up against [this bug](https://github.com/facebookincubator/create-react-app

Can you please add has many Not-Eloquent relation to the demo application? It's a bit difficult to understand how I should implement all this interfaces and abstract classes to make my entities work 😄
Thanks

We will be doing something akin to #91

• A better split between unit, acceptance and e2e with a 70, 20, 10 split
• No more hand building requests, need factories for that
• Clean up naming convention.

Unless the pagination links are removed from the URI passed to Document::addPaginationLinks() the output will be duplicated:

	"links": {
		"first": "https:\/\/api.acme.net\/users?page%5Blimit%5D=5?page%5Blimit%5D=5",
		"next": "https:\/\/api.acme.net/users?page%5Blimit%5D=5?page%5Blimit%5D=5&page%5Boffset%5D=5"
	}

It should be clearly documented that the passed URI must be

This page is still running the V1 setup, it is referencing the old setup api's:

setEndpointHost, setEndpointPath, setAccessToken, setHeader and setHeader

These are all been deprecated in favour of the setAxiosConfig api.

https://github.com/redux-json-api/redux-json-api/blob/master/docs/set-up-configure.md

So just a friendly hint and maybe I'm not having the brightest day, but without much prior knowledge to the topic of json:apis I found your documention rather hard.
You get very much into the Initializer and the advanced features, but skip the basic parts like the Model defining process and how the attributes get mapped. (Having a "post" as a type here is just a tad misleading btw.)
If you cou

Hi,

When configurating the the PyJFuzz library for generating messages you can specify a specific fuzzing level 1 to 6. I was not able to find in the documentation what these levels mean exactly and what the difference is when picking another level. Can you make that more clear in the README or something?

Best regards,
Ivar Derksen

Hello,

I discovered Laravel and Lumen. I want to create a clean API. I would like to implement JSON API. I tested your library.
I discovered some errors in the documentation.

For the controller, it would indicate the need to put the controller in the directory "app/Http/Controllers/Api".
Since the namespace of the controller is not correct. There must be "App/Http/Controllers/Api".

In the r

Whilst the relationships work find and are well documented for reading - I am finding that I really do not know what I am doing when trying to use them during creation / updating of a resource. I was expecting this to work :-

forum = Forum.find(1).first
forum.posts << Post.find(5)
forum.save

This is assuming that a forum has many posts

Please can you add some examples to the readme to