Open weierophinney opened 4 years ago
Hi,
We shoudl also have a look at the refactor I did: https://github.com/zendframework/zend-inputfilter/issues/13
It simplified A LOT of things regarding to continue/allow_empty, stateless, refactored collection input filter... and a lot of other things. I did that a lot of time ago so I don't exactly remember, but this refactor mostly answered to most of the problems you are referring to :).
I will start working again on this, but first we'll need to have the stateless zend-validator and zend-filter.
Originally posted by @bakura10 at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-134507082
What is the status for the stateless input filters?
Originally posted by @RalfEggert at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-169792626
@RalfEggert Still in planning stages, though @bakura10 has done significant work on a fork he's maintaining. (I've asked him to document usage so I can actually evaluate the changes and the migration/usage impact.)
Originally posted by @weierophinney at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-169793302
Stateless input filter can only be done once we have stateless validators :).
Originally posted by @bakura10 at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-169793524
What do You think of renaming this component to something more accurate? I dont know, maybe inputparser? Inputfilter name is very confusing. What it does is filtration and validation. For someone who does not know Zend libraries it is hard to find the difference between filter and inputfilter.
Originally posted by @xorock at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-224513840
@bakura10 @weierophinney What is the status of this? Is it being abandoned in favor of the eventually up-coming zend-datavalidator
in the future?
Originally posted by @thexpand at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-412441804
@thexpand
Is it being abandoned in favor of the eventually up-coming
zend-datavalidator
in the future?
Please keep in mind that the input-filter is doing something more than validation for values. The zend-datavalidator
will replace zend-validator and not zend-inputfilter.
Originally posted by @froschdesign at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-412447700
That's actually still to be determined. There's a fair amount of cross over in how validators and inputs report errors, and my current work has been around adding the input/data set functionality to the new component.
On Mon, Aug 13, 2018, 3:39 AM Frank Brückner notifications@github.com wrote:
@thexpand https://github.com/thexpand
Is it being abandoned in favor of the eventually up-coming zend-datavalidator in the future?
Please keep in mind that the input-filter is doing something more than validation for values. The zend-datavalidator https://github.com/weierophinney/zend-datavalidator will replace zend-validator and not zend-inputfilter.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-412447700, or mute the thread https://github.com/notifications/unsubscribe-auth/AABlV7_eltEVvx0oTyH-eRa0wXVewqOKks5uQTs_gaJpZM4FxUDt .
Originally posted by @weierophinney at https://github.com/zendframework/zend-inputfilter/issues/39#issuecomment-412487379
Proposal of roadmap for next major versions.
V3: V3 should silently fail if any deprecation feature is used. i.e. No file/method removal/rename is allowed.
V4: V4 does not (currently) restrict any bc break type.
Originally posted by @Maks3w at https://github.com/zendframework/zend-inputfilter/issues/39