'suggest' parameter in combination with 'fformatter' parameter

[wlorenzetti]

Closes: #810

With this PR now is possible apply suggest parameter for /vector/api/data API REST in combination with 'fformatter' parameter.

The suggest parameter will contain the fformatter field name.

[Raruto]

KO: 500 internal server error

GET /vector/api/data/qdjango/3/buildings_2f43dc1d_6725_42d2_a09b_dd446220104a/?suggest=id_buildings%7Cala&ordering=id_buildings&formatter=1&fformatter=id_buildings

HTTP 500 Internal Server Error
Allow: GET, POST, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "result": false,
    "error": {
        "code": "servererror",
        "message": "A error server is occured!",
        "data": "id_buildings doesn't belongs from layer!"
    }
}

docker logs:

2024-04-12 16:06:07 Internal Server Error: /vector/api/data/qdjango/3/buildings_2f43dc1d_6725_42d2_a09b_dd446220104a/
2024-04-12 16:06:07 Internal Server Error: /vector/api/data/qdjango/3/buildings_2f43dc1d_6725_42d2_a09b_dd446220104a/
2024-04-12 16:06:07 ERROR:django.request:Internal Server Error: /vector/api/data/qdjango/3/buildings_2f43dc1d_6725_42d2_a09b_dd446220104a/

[wlorenzetti]

#811 (review)

id_buildings doesn't exists inside buildings_2f43dc1d_6725_42d2_a09b_dd446220104a. In this case is the SuggestFilterBackend tha fails. It works with related layers in example buildings_rating_3d535fae_fd04_4df6_b6ff_8cbd13df078f as reported int the issue #810

[Raruto]

@wlorenzetti I couldn't say why the search widget requested a wrong layer.

Now the building relation search works properly:

Can you test the autocomplete address search as well?

It should return something, but instead I get no results:

[wlorenzetti]

@Raruto I'm checking this issue, it's very strange, it seems to be due to qgis-server but I have to investigate further.

[wlorenzetti]

@Raruto what version of qgis-server are you using?

[Raruto]

what version of qgis-server are you using?

@wlorenzetti 3.28.5-Firenze

[wlorenzetti]

Ok @Raruto I understand the problem address has a Value Relation widget so suggest param workd on origin address values (A101, A103,...). I think this is is a case not implemented at now.

[Raruto]

Yes, that case was not handled in v37 either.

Just to remind you, you should test your API changes against the JS code that comes from this PR #787, which depends entirely on the fformatter parameter. *

* ie. that always performs the same kind of HTTP call (regardless of widget type), thus making the overall logic much simpler 😉.

[wlorenzetti]

@Raruto I just speak with @leolami and @volterra79, this feature didn't work at now. So I'll remove the AutoCompleteBox choose when the field has a ValueRelation widget.

[Raruto]

As far as I'm concerned this PR is fine for fix #810 (a RelationReference search).

I'll remove the AutoCompleteBox choose when the field has a ValueRelation widget.

Quite brutal solution, but ok.