phoenix changelog

Hey there, fabulous users! We've got some exciting updates for you, so let's dive right in! 🎉

Improvement: Email Address Validation 📨
No more sneaky commas in your email field! We've beefed up our email validation game to make sure you enter just one email address, and one only. The new regex is a stickler for rules, disallowing any cheeky commas or semicolons. Rest assured, your email will be a solo act, and it'll be in tip-top shape for authentication! 🚀

Improvement: Clearer Documentation for Code Building 📚
We've polished up our docs to make your life easier. Now, when you're running multiple instances of your app, you'll know exactly how to manage your code reloading with the MIX_BUILD_PATH environment variable. No more mix-ups with build directories—just smooth sailing and clear guidance for a seamless developer experience. Happy coding! 💻✨

That's all for now, folks. Keep those updates coming, and stay awesome! 🌟

Included Commits

2024-12-21T10:00:44 See commit

This commit addresses an issue in the email validation logic within the authentication schema of a Phoenix application. Specifically, it updates the regular expression used in the validate_format function to prevent users from entering multiple email addresses separated by commas in the email field. The new regex ensures that the input contains only a single valid email address by disallowing characters such as commas and semicolons.

In addition to modifying the regex, the commit also maintains the existing validation checks, including the requirement for the email field and a maximum length of 160 characters. This enhancement improves the robustness of the email validation process, ensuring that users provide a correctly formatted single email address during authentication.

Files changed

  • priv/templates/phx.gen.auth/schema.ex
2024-12-21T10:04:54 See commit

This commit updates the documentation in the lib/phoenix/endpoint.ex file to refer to the MIX_BUILD_PATH environment variable instead of the previously mentioned MIX_BUILD. The change clarifies how to manage code reloading in development when running multiple instances of the same application simultaneously.

Specifically, the documentation advises users to either enable code reloading in only one of the application instances or to set the MIX_BUILD_PATH variable, which allows for distinct build directories, thus preventing conflicts during recompilation. This enhancement aims to improve the developer experience by providing clearer guidance on managing environment variables related to application builds.

Files changed

  • lib/phoenix/endpoint.ex