• Good morning, I wanted to ask if there is an integration planned in the future that prevents the form from sending data that is not present, for example in a select box. For example, let’s imagine a select box with the options “A”, “B” and “C”. If I access from the frontend I will obviously find the selectable options and send the form enhanced with the chosen option. However, if I inspect the html code and modify the select box on the client side, adding for example the “D” option, I realized that the form sends the information by dragging the option that was not present upstream (precisely “D “). Is there a way to avoid this type of “hack”?
    Now I have given the example with the select box but the behavior can be applied to any other type of data (for example I can change the type of an input from numeric to alphanumeric etc.)
    Thank you very much for the attention.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Good point. As you described, the current user input validation accepts values that are not defined in a select menu option. While this is helpful in cases where you manipulate values on frontend, there are side effects such as inaccurate config validation. You can apply stricter rules utilizing the enum SWV rule, and I’m planning to make this applied by default.

    Thread Starter phaser32

    (@phaser32)

    Thank You for reply Miyoshi!

    I’ll wait for a future integration

    Warm regards

    Ale

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Control of the data sent’ is closed to new replies.