Support for list features

[BertrandRenault]

Issue

Fixes #81

Description

Allow user to define restricted list of values for features (attributes)
Define in db.json "features_values"
exemple:

  "features_values": {
    "main": {
      "quality": {
        "restricted": true,
        "values": ["good", "bad"]
      },
      "quantity": {
        "restricted": true,
        "values": ["few", "standard", "many"]
      }
    },
    "objects": {
      "category": {
        "restricted": false,
        "values": ["apple", "banana", "orange"]
      }
    }
  }

If a feature is not defined here, or not restricted, then Pixano(back) will look for existing values in corresponding table(s) and merge with existing defined values.

Features are considered as not restricted if not explicitly defined as restricted

• remove "categories" in db.json
• replace "categories" in tests
• manage "supercategory": filled if exists, else ""
• replace "categories" in importers
• replace "categories" in storybook

[timothee-LJN]

I'm wondering if isSearchInputEnabled or just isSearchEnabled would be more relevant here?

[cpvannier]

With the ongoing backend refactor, I wonder if it is worth it to merge this PR now, as it will likely create some merge conflicts.

Also, renaming scene and sceneFeatures into main and mainFeatures in the frontend is not really relevant anymore, as the refactor replaced main by item in the backend.

[timothee-LJN]

ok, we put it on hold then?

[BertrandRenault]

With the ongoing backend refactor, I wonder if it is worth it to merge this PR now, as it will likely create some merge conflicts.

Backend refactor will have merge conflict, for sure. But postponing this PR will not really change that. And merging this PR after backend refactor would cause too much new merge conflict for this PR, that we can avoid by merging now. This way there will be one conflict resolution instead of 2, and the added functionality too.

Also, renaming scene and sceneFeatures into main and mainFeatures in the frontend is not really relevant anymore, as the refactor replaced main by item in the backend.

this PR await since 3 weeks... there is plenty of "main" everywhere... Why not open a "naming refactor" PR ?

[timothee-LJN]

I have an error here when I'm editing the image :