fix: fields=all returns customized field values

[stephanegigandet]

fields=all had a difficult to understand behaviour: it returned all raw fields, without customization. Which meant that asking for packagings in v3 would return a different packagings field that asking for all in v3.

This PR:

• adds a new fields=raw option, to get whatever is stored in MongoDB
• makes values from fields=all customized
• add the possibility to request all + some fields that are computed on requests (e.g. fields=all,attribute_groups or fields=updated,knowledge_panels
• adds corresponding tests

[alexgarel]

LGTM. It's a good change.

I only have small suggestions

[alexgarel]

Why is the explanation below not in the content schema with an entry "fields" ?

[stephanegigandet]

There is a fields entry in the content schema for the request (which is above), below is the content schema of the response (which does not have a fields entry, but is affected by the fields parameter in the query)

[alexgarel]

Do you understand why you have this flip-flap between string and raw numbers ?

[stephanegigandet]

@alexgarel it's an issue with JSON:PP which select the type (string or number) based on what the last use of the scalar was. I tried to find out what exactly was using those scalars in a string context (like a debug dump function), but I failed.

https://docs.mojolicious.org/JSON/PP#PERL---JSON

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information