Improve input element selection logic

[fglueck]

allows something like this:
FormDataJson.toJson($(':input:not(.no_filter,button,[name="pool[]"])','#filter'),{includeDisabled: true, uncheckedValue: 0})

[brainfoolong]

Hi. Thanks for your PR. Unfortunately, this is not something i can merge.

First, it contains bugs checkEl instanceof Object but Object has not length attribute.

Second, it is not supposed to work like that. Such a feature is already implemented with an option parameter. To filter out any inputs from the list, you can use inputFilter to reduce the list of elements. Example -> https://github.com/brainfoolong/form-data-json?tab=readme-ov-file#read-form-input-values-but-filter-out-for-example-all-password-fields

[fglueck]

Argh... sorry, thats true. But I don't want to filter Elements, I want to generate a json about different elements from different scopes.
Like this:
$('#filterelemente :input, table.hdr :input')

[brainfoolong]

I understand. I will think about another solution that do not create a bit of an ambiguous state by this kind of type checking.

Currently your change, even if the bug is fixed, does expect that when jQuery object is passed, it always think just one element is required to be a form, but that's not good, because it blocks all the cases where you can pass a single input.

It will need some time for it, but there will be a solution, sooner or later.

[fglueck]

Now, it is possible that checkEl is a already a array (list of elements) or an jquery array or old behavior....

[brainfoolong]

Now you actually introduced a new bug when just passing a normal string (selector).

Don't bother fixing it, i'll implement another logic.

[fglueck]

I am ashamed, I tested only with array and jquery elements...