Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could requirement to neos/fusion-form be changed to suggestion? #2

Open
lorenzulrich opened this issue Apr 28, 2023 · 0 comments
Open

Comments

@lorenzulrich
Copy link

First of all, thanks for implementing SymfonyMailer for Neos. We have quite a few Flow-only projects that need to send mails, and as SwiftMailer is EOL, migrating to SymfonyMailer would make sense.

From reading to code, only https://github.com/sitegeist/Sitegeist.Neos.SymfonyMailer/blob/ba1ae976a3546d465124ec0f5b9bcfe8a7dcc85f/Classes/Action/SendMailAction.php has real dependencies to Neos and Neos.Fusion.Form. Personally I think this could just be a concern of Neos.Fusion.Form instead of the SymfonyMailer package.

But even if you don't agree about this, would you be willing to lower the dependencies so it could be used with Flow only?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant