size, lte, and gte rules are comparing numeric value instead of string length when applied to text fields

[MontherTwisi]

When using validation rules such as size, lte, and gte on a text field, the validation currently treats the input as a numeric value rather than validating against the character length of the string. This results in unexpected behavior — for example, setting size:3 on a text field causes it to fail unless the input is literally "3" or "003", instead of checking if the string is 3 characters long.

Steps to reproduce the behavior:

Create a simple text field.

Add a size:3 rule (or lte:5, gte:2).

Try inputting a 3-character string like "abc" or "123".

Validation fails, unless the input is a numeric value matching the number (e.g. 3).

The size, lte, and gte rules should evaluate the length of the string input when used on a text field, not its numeric value. This is how Laravel validation works with strings and matches the intuitive expectation for frontend validation.

Actual behavior
The rules interpret the input value numerically — treating "abc" as invalid for size:3, while "3" passes.

[adamberecz]

I wasn't able to reproduce this in the sandbox, can you maybe help with it?
https://stackblitz.com/edit/github-jercdbra?file=src%2FApp.vue

You are right, when min is set it should validate against length not value unless numeric or integer rule is added.

[adamberecz]

Hi @MontherTwisi!

I would like to make it clear that I help all companies and developers here in GitHub regardless whether they have a paid subscription or not. This happens on a best effort basis and yes, there is a priority support feature for enterprise clients that can shorten the expected response times.

our company has officially paid for the builder subscription

No, they haven't yet and neither we have a signed support agreement in place. Please check with your company regarding this as this might be a source of misalignment in expectations.

Anyways, thank you for providing the example code. Please refer to our guide regarding size type validation rules for more info on why this isn't working.

number and number_1 are numeric input types (have numeric rule) so they are treated as numbers. So the text will have an expected length between number and number_1. If you want the text to be an expected number between number and number_1 you have to add numeric rule to text too.

This stands true for your original description and probably that's why I wasn't able to reproduce it. If you have numeric rule added to a field, it will be treated as a number and min, max, etc will check for value not length.

Nevertheless, if you think there is an issue with this in any other case, please send a reproduction and I will be happy to look into it.

[MontherTwisi]

Hi @adamberecz

Thank you for the clarification, and I sincerely apologize for any misunderstanding or the impression that support is limited based on subscription status. That was not my intention at all.

I truly appreciate the time and effort you dedicate to supporting the community here, and I fully understand that help is provided on a best effort basis unless there is a formal support agreement in place.

What I meant that even if the rule was not a number, the validator doesn't validate against the length of string in all cases, it always validates against the digit:

    schema: {
        text: {
          type: 'text',
          label: 'Text',
          rules: [
            'lte:number',
            'gte:number_1',
            'string',
          ],
        },
        number: {
          type: 'text',
          inputType: 'number',
          rules: [
            'nullable',
            'string',
          ],
          autocomplete: 'off',
          label: 'Number',
        },
        number_1: {
          type: 'text',
          inputType: 'number',
          rules: [
            'nullable',
            'string',
          ],
          autocomplete: 'off',
          label: 'Number',
        },
      },

Please check this case and advice.
Thanks one more time.

[adamberecz]

With this example the following happens:

• I enter foo into text
• I enter 333 into number (text should be lte than length so <=3)
• I enter 22 into number_1 (text should be gte than length so >=2)

And it accepts the input for foo.

If I change foo to foobar it will throw a validation error, because text is now longer than number (333) so if I change number to 666666 it passes again.

See it in action here:
https://stackblitz.com/edit/github-jercdbra-hboyf5w9?file=src%2FApp.vue

Can you confirm?

[MontherTwisi]

What is expected on which documented for any "size" related rules is when you add 30 in the number field, the text field should have a less than equal "number of characters" in the number field, so adding 5 in the number field should give me the ability to add 4 or less character length , check the screenshot result for the same sandbox you added:

Based on the screenshot and documentation, I should be able to add up to 100 characters and at least 2 characters, or at least this is what we expected from our point of understanding of the documentation.

Please advice if we were trying to use the rule in a wrong way.
Thanks,

[adamberecz]

Minor misunderstanding:

the validator doesn't validate against the length of string in all cases, it always validates against the digit

I took this as the issue not the expected behavior.

This issue I can confirm.

I've rolled out a fix: https://github.com/vueform/vueform/releases/tag/1.12.11