In D7357#191292, @vlorentz wrote:

Could you make a different page for each tab, so it works with browser history?

Yes but then after that we need to force push that branch anyway.
For now, we are incrementally progressing to add the missing coverage on the views.
We should never have started mixing multiple views in commits but it's done that way now...
So there fight.

Landed in b6d540d2e5fa.

@anlambert will have to force

I am abandoning this and will submit a new diff where I will separate the datatables listing endpoint from the Web API one (the advantage is that requests will not be throttled) and handle the remaining comments from @vlorentz.

In D7344#191127, @vlorentz wrote:

The reason to throttle it is to avoid resource abuse; which is not limited to the API

In D7344#191125, @vlorentz wrote:

the advantage is that requests will not be throttled

Why throttle the public API endpoint but not the datatables endpoint?

I am abandoning this and will submit a new diff where I will separate the datatables listing endpoint from the Web API one (the advantage is that requests will not be throttled) and handle the remaining comments from @vlorentz.

Landed in 1bf17d6a75fd.

Landed in 294a95c711bc.

Landed in 26748e56ecce.

Rebase

Rebase

Update: Address @ardumont comments

Update: Address @vlorentz comments

Could you move all this new code in a new module and call it from the loader? loader.py is already uncomfortably large.

Fix status update

Update: Rework next request statuses allowed code

Landed in 130e9faa9bca

Add duplicate create check, return 409 (conflict)

Rebase

Abandoning this as public API v2 will be built on top of GraphQL.

Fix commi message

Keep help page available after all.

In D7245#188786, @moranegg wrote:

Is it necessary to delete completely the help.html template?
I know it will not be accessible from the menu, but maybe it is safer to keep it around..