Add `items` action about valibot HOT 10 CLOSED

Thank you!

from valibot.

I can see that. I'm OK with checkItems, so go on :D.

from valibot.

Thank you. I saw you have created more Items actions, which is nice :)

from valibot.

I have started to work in this issue.

from valibot.

Nice, thanks for letting me know.

from valibot.

I am still unsure of the correct name. The advantage and difference of this action is that a issue is automatically associated with the item that caused the problem. items and iterate do not reflect this in my eyes. What do you think about checkItem or forEach? The name checkItem is very clear and easy to read. forEach might also work as I plan to add actions for the other iterator methods like sort and filter as well.

from valibot.

I ran into another problem. Since we already have a map schema, I can't add a map action for transforming arrays due to the name collision. One solution to this problem is to call the map action forEach. Another solution might be to add the suffix Item or Items to these functions: everyItem, filterItems, findItem, mapItems, reduceItems, someItem. The last solution would also work well with checkItems.

from valibot.

What about checkEach? I think it reflects what it does. checkItems it's a good name as well.
I agree with you when you say that items or iterate doesn't reflect what it does.

from valibot.

checkEach is great, but I really like the Item and Items suffixes for the iterator actions. This makes it even clearer and prevents other naming conflicts in the future. If we go this way, checkItems would make more sense in my eyes.

from valibot.

Valibot v0.33.1 is now available 🎉

from valibot.