phoenix changelog

Here's the latest scoop on what's been cooking in our codebase! We've been busy adding new features, making improvements, and squashing bugs to make everything run smoother than a cat on a freshly polished floor. Check out the highlights below! 🐾✨

  • New feature: We rolled out a shiny new module, PlugRouterWithVerifiedRoutes, which implements the Phoenix.VerifiedRoutes behavior. It comes with a simple HTTP GET route at "/foo" responding with a 200 status and "ok" text. Plus, it includes implementations for formatted_routes/1 and verified_route?/2 to keep your routes in check. 🚀

  • Improvement: Our guides got a major facelift! We've revamped the documentation, adding new sections on data modeling, contexts, and FAQs. Existing guides like directory structure and Ecto have been polished for clarity. Now, navigating our docs is as smooth as butter! 📚✨

  • Improvement: Say hello to the unminified daisyUI! We've updated our vendored directory with the unminified version from 5.0.8, making it easier to tweak and debug. The main.css and JavaScript updates bring a fresh breath of simplicity and style to your UI components. 🌼🎨

  • Improvement: To avoid confusion, we've added a requirement for at least one attribute when using phx.gen.html and phx.gen.live generators. This ensures you won't accidentally create incomplete implementations. Now, every generation is a complete package! 🎁

  • Bugfix: We corrected an oopsie in the changelog! It mistakenly stated that layouts with modules were deprecated, but it's actually the ones without modules. Now, the changelog sings the right tune. 🎶

  • Bugfix: Our SQLite3 integration tests are back on track! We fixed formatting issues in application.ex files and updated test cases to align with the SQLite3 adapter. Everything's running like a well-oiled machine! 🛠️

  • Bugfix: The recreate_default_css script now correctly references main.css instead of the outdated app.css. This fix prevents any hiccups in CSS generation, keeping your styles fresh and consistent! 🎨

  • Chore: We've officially deprecated some soft-deprecated controller entry points. The codebase and tests have been updated to reflect these changes, nudging developers towards best practices. Out with the old, in with the new! 🔄

We're all about making things better, faster, and more fun. Keep your eyes peeled for more exciting updates! 🎉

Included Commits

2025-03-21T08:48:25 See commit

This commit addresses an issue with the recreate_default_css script by updating it to reference main.css instead of the outdated app.css. The change was necessary because the CSS file name was modified in a previous commit (87102f033687293b8909e5316d6a52fcea6a7cd7), but the script did not reflect this update, potentially leading to errors or inconsistencies in the CSS generation process.

The modifications include reading from and writing to main.css in the specified directories, ensuring that the script correctly processes the new file. Specifically, the script now reads the contents of main.css, replaces the theme declaration, and writes the updated styles to the appropriate output file. This change enhances the functionality of the installer by aligning it with the current file structure and naming conventions.

Files changed

  • installer/recreate_default_css.exs
2025-03-21T08:49:59 See commit

This commit introduces the use of an unminified version of daisyUI, effective from version 5.0.8, which is now included in the vendored directory. The update notes have been integrated into the main.css file, and the unminified JavaScript file has been added to the installer. The modifications primarily involve significant changes to the daisyui.js file, with over 1,000 lines of code altered, reflecting the new unminified format.

In addition to the JavaScript updates, there are minor adjustments made to the main.css and default.css files. The CSS changes include the addition of comments for fetching the latest daisyUI version, as well as various styling updates to button and badge components. These adjustments aim to improve the overall styling consistency and functionality within the application, ensuring better integration of the daisyUI plugin.

Files changed

  • installer/templates/phx_assets/daisyui.js
  • installer/templates/phx_assets/main.css
  • installer/templates/phx_static/default.css
2025-03-21T15:42:30 See commit

The commit titled "Guides revamp (#6131)" introduces a comprehensive update to the project's documentation, particularly focusing on data modeling and related topics. New guides have been added, including detailed sections on contexts, cross-context boundaries, FAQs, in-context relationships, examples, and a beginner's guide to creating a context. These additions aim to enhance the understanding of data modeling for users.

Additionally, several existing guides have been modified to improve clarity and provide updated information. Key documents such as the directory structure, Ecto guide, overview, and telemetry have been revised, alongside the testing contexts guide. The changes reflect an ongoing effort to streamline the documentation and make it more accessible to users, ensuring they have the necessary resources for effective implementation and troubleshooting.

Files changed

  • guides/data_modelling/contexts.md
  • guides/data_modelling/cross_context_boundaries.md
  • guides/data_modelling/faq.md
  • guides/data_modelling/in_context_relationships.md
  • guides/data_modelling/more_examples.md
  • guides/data_modelling/your_first_context.md
  • guides/directory_structure.md
  • guides/ecto.md
  • guides/howto/swapping_databases.md
  • guides/introduction/overview.md
  • guides/introduction/up_and_running.md
  • guides/telemetry.md
  • guides/testing/testing_contexts.md
  • mix.exs
2025-03-22T13:06:34 See commit

This commit focuses on deprecating certain controller entry points that have been marked as "soft-deprecated" in the Phoenix framework. The changes made include modifications to several files, notably the primary controller file (lib/phoenix/controller.ex) and various test files across the router and controller directories, indicating a comprehensive update to ensure that the deprecation is properly reflected in both the codebase and its associated tests.

Additionally, the CHANGELOG.md file has been updated to document these changes, signaling to developers that they should transition away from using the deprecated entry points. This step is part of ongoing efforts to streamline the framework and encourage best practices among users.

Files changed

  • CHANGELOG.md
  • lib/phoenix/controller.ex
  • test/phoenix/controller/controller_test.exs
  • test/phoenix/controller/pipeline_test.exs
  • test/phoenix/router/forward_test.exs
  • test/phoenix/router/pipeline_test.exs
  • test/phoenix/router/resource_test.exs
  • test/phoenix/router/resources_test.exs
  • test/phoenix/router/routing_test.exs
  • test/phoenix/router/scope_test.exs
2025-03-24T18:23:58 See commit

The commit addresses an error in the changelog regarding the deprecation of layout specifications in a Phoenix framework release. Previously, the changelog incorrectly stated that layouts with modules were deprecated; however, the actual deprecation pertains to layouts specified without modules. This clarification is important for developers to understand the correct usage of the put_layout function.

In the updated changelog, the wording has been corrected to reflect that specifying layouts without modules, such as put_layout(conn, :print) or put_layout(conn, html: :print), is indeed deprecated. The commit includes modifications to the CHANGELOG.md file, making a single addition and deletion, along with two changes to ensure accurate communication of the deprecation status to users.

Files changed

  • CHANGELOG.md
2025-03-25T13:26:43 See commit

This commit addresses issues in the SQLite3 integration tests by modifying the application files and test cases to ensure proper functionality. Specifically, changes were made to the application.ex files in both the single app and umbrella templates. The modifications involve correcting the formatting of the Ecto.Migrator configuration, ensuring that the repos and skip options are properly structured within the same line. This enhances the clarity and correctness of the application setup for SQLite3 integration.

Additionally, the commit updates the app_with_sqlite3_adapter_test.exs file to replace references to DefaultMysqlAppWeb with DefaultSqlite3AppWeb in the router definitions, aligning the test cases with the SQLite3 adapter. This ensures that the integration tests accurately reflect the intended configuration and routing for applications using the SQLite3 database adapter, thereby improving the reliability of the tests.

Files changed

  • installer/templates/phx_single/lib/app_name/application.ex
  • installer/templates/phx_umbrella/apps/app_name/lib/app_name/application.ex
  • integration_test/test/code_generation/app_with_sqlite3_adapter_test.exs
2025-03-25T16:43:48 See commit

This commit introduces a new module, PlugRouterWithVerifiedRoutes, which implements the Phoenix.VerifiedRoutes behavior. The module defines a simple HTTP GET route at "/foo" that responds with a 200 status and the text "ok". It also provides two required implementations: formatted_routes/1, which returns a list of routes with their HTTP verb and labels, and verified_route?/2, which checks if a given path corresponds to the defined route.

Additionally, the commit modifies the test file verified_routes_test.exs by moving the definition of PlugRouterWithVerifiedRoutes to a more appropriate location before it is used. The changes include removing the previous definition of the router from within the test module and ensuring that the router is correctly referenced in the ForwardedRouter module. Overall, the commit enhances code organization and clarity by defining the module before its usage.

Files changed

  • test/phoenix/verified_routes_test.exs
2025-03-25T19:04:21 See commit

This commit introduces a requirement for at least one attribute when using the phx.gen.html and phx.gen.live generators in the Phoenix framework. Previously, it was possible to run these commands without specifying any attributes, which could lead to confusion or incomplete implementations. The changes involve adding a validation check in both the phx.gen.html and phx.gen.live modules, which raises an error if no attributes are provided. This ensures that developers are prompted to define at least one attribute, enhancing the clarity and usability of the generators.

In addition to the validation logic, the commit includes updates to the documentation to reflect this new requirement. The examples provided in the documentation have been modified to emphasize the necessity of including attributes when invoking these generators, thereby providing clearer guidance to users. Overall, this change aims to improve the developer experience by preventing potential issues stemming from the omission of attributes in resource generation.

Files changed

  • lib/mix/tasks/phx.gen.html.ex
  • lib/mix/tasks/phx.gen.live.ex