String props that are integer values aren't treated as strings

I'm an idiot. Just use an integer type. I'm so tired :/

Thank you @kristen pol for updating this! I'm keeping this as a minor bug report as it impacts DX. This may be still desired because of that.

We can add the prop with type integer as per the below code. It will generate a new filter level with no error.

    level:
      type: integer
      title: Level
      description: 'Semantic level: 1, 2, 3, 4.'
      default: 2
      enum:
        - 1
        - 2
        - 3
        - 4
      examples:
        - 2

See comment #2 above

yes, Kristen pol. Thanks for the comment. I added the code for better visibility.

Moving back to active .

Running into this for the "data card" because you can have "+100" or "50" or similar. If it's a string, then the "50" won't work, but if it's an integer than "+100" won't work. Moving to normal.

AFAICT this is once again a duplicate of 🌱 [META] Redux sync on ALL prop types, not just ones with a single [value] property Active , because the options_select field widget for the list_integer field type generates something like

<select>
…
<option value="3">3</option>
<option value="4">4</option>
…
</select>

…  i.e. those are <em>string</em> values in the <code>value

attribute for each <option>, the client-side must know when to map those to integers.

I assume this is related:

🐛 Numeric field input crashes contextual settings panel Active

Duplicate of 🐛 Numeric field input crashes contextual settings panel Active