1.7.4 Support Symfony 7

What's Changed

• Allow Symfony 7 by @svandervlugt in #38

Full Changelog: 1.7.3...1.7.4

Add support for Symfony 6

Merge pull request #37 from hostnet/fix-tests

Fix failing unit tests

Update phpcs-tool to 9.1.0 with Hostnet-Level-1

• Updates phpcs-tool to 9.1.0 with Hostnet-Level-1

php 8 support

1.7.1

added php 8 support

Symfony 5 support

This release includes

• #29 Symfony 5

special thanks to @GawainLynch for contributing

End of EOL php and symfony versions

• Remove eol support, and upgrade most packages #30

Prevent leaking sensitive request data from array callables

Don't expose request stacktrace in call_user_func

When call_user_func runs a callable that throws an exception, the
exception stacktrace will contain the request object. When a logger
parses the array of functions, it might cause this processor/formatter
to call the `__toString()` function on the Request object, which will
then contain all request information, which includes passwords when
sent as post body.

See: Seldaek/monolog#1138

Support for sf4

This patch as supports for Symfony 4.0.

Fixes a BC break regarding 2.x form types

After #19 it was no longer possible to use form types that were not a FQCN, this broke support for Symfony 2.x. This release fixes this particular bug.

Added setFormSubmitProcessor to the HandlerConfigInterface

Added a way to apply a custom form submit processor to the handler if you require more fine-grained way to handle your form.

By default the ::handleRequest() is used, but if you need want to do something differently you can do that as follows:

public function configure(HandlerConfigInterface $config)
{
    $config->setFormSubmitProcessor(function (FormInterface $form, Request $request) {
        // taken from the Symfony docs example
        $form->submit($request->request->get($form->getName()));
    });
}

Example it take from the symfony docs: https://symfony.com/doc/current/form/direct_submit.html