Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/phoenixframework/phoenix. Pull mirroring updated .
  1. Nov 07, 2018
  2. Nov 06, 2018
    • Tan Jay Jun's avatar
      Document Phoenix.Channel callbacks (#3130) · d747637a
      Tan Jay Jun authored
      d747637a
    • Jeff Kreeftmeijer's avatar
      Remove extra newline in generated context test cases (#3129) · bf1872be
      Jeff Kreeftmeijer authored
      Currently, context tests generated by running the html generator (`mix
      phx.gen.context Accounts User users name:string`), produce a test with
      an extra line with some trailing whitespace (illustrated with dots
      here):
      
              test "update_user/2 with valid data updates the user" do
                user = user_fixture()
                assert {:ok, %User{} = user} = Accounts.update_user(user, @update_attrs)
      
          ······
                assert user.name == "some updated name"
              end
      
      This patch removes both newlines from the template, resulting in a
      generated test like this:
      
              test "update_user/2 with valid data updates the user" do
                user = user_fixture()
                assert {:ok, %User{} = user} = Accounts.update_user(user, @update_attrs)
                assert user.name == "some updated name"
              end
      bf1872be
    • Gerry Shaw's avatar
      Do not assume project in current directory (#3131) · 9cf69447
      Gerry Shaw authored
      Correctly prints `cd path/to/project` when project is created in a
      nested directory.
      9cf69447
  3. Nov 05, 2018
  4. Nov 02, 2018
  5. Nov 01, 2018
  6. Oct 31, 2018
  7. Oct 30, 2018
  8. Oct 29, 2018
  9. Oct 26, 2018
  10. Oct 25, 2018
  11. Oct 24, 2018
  12. Oct 21, 2018
  13. Oct 20, 2018
  14. Oct 17, 2018
    • Gary Rennie's avatar
      Use FunctionClauseError for Phoenix.ActionClauseError (#3102) · 054a1c80
      Gary Rennie authored
      Using `FunctionClauseError` results in showing the available clauses
      when displaying the error message. This also renders nicely in the plug
      exceptions page.
      
      Instead of using `plug_status` in the exception, the `Plug.Exception`
      protocol is explicitly defined for the `ActionClauseError` to allow easy
      transitioning between `ActionClauseError` and `FunctionClauseError`.`
      
      This closes #2657
      054a1c80
  15. Oct 15, 2018
Loading