Oban Web v2.10.0 final is out! As always, the live demo is available for you to play with.

The release candidate phase is over; this is a general release with bug fixes and a few small enhancements. Thanks to everybody who tested the RC and gave bug reports and feedback

The full changelog of each RC and the final point-0 release are inlined below:

v2.10.0 — 2023-10-12

Enhancements

• [Jobs] Append and submit filter suggestions on click

  Previously, clicking a suggested value injected it into the input but didn’t submit it as a filter. That was unexpected, and led to an odd “deletion” of previous values when typing multiple filters at once. Clicking on a suggested value immediately submits it as a filter now.

• [Jobs] Improved json path suggestions

  Auto submission exposed an issue with json path completion, i.e. path suggestions lacked a final : or . to indicate if it was a full qualifier or part of a path. Now it’s clear whether an args or meta suggestion is part of a nested object path (.), or a final key (:).

• [Jobs] Add filtering by a list of ids, e.g. ids:1,2,3

  It turns out this is a commonly used feature, especially in a staging environment and by testing teams.

Bug Fixes

• [Resolver] Only use a conservative query limit for completed jobs

  Due to the loose application of threshold queries, the 100k limit caused confusion for other states with only a handful of jobs, e.g. retryable. Now the limit is only applied to completed jobs by default and :infinity for all other states.

• [Jobs] Parse entire term as an integer when filtering

  Values, such as UUIDs that start with a digit, were incorrectly considered an integer and couldn’t be used in filtering.

• [Job Details] Prevent cancelled/discarded jobs showing completed

  The timeline component incorrectly displayed jobs that weren’t completed or executing as completed.

v2.10.0-rc.3 — 2023-09-24

Enhancements

• [Resolver] Prevent dashboard access with :forbidden access

  The dashboard now offers authentication by checking access on mount via resolve_access/1. Returning {:forbidden, path} will halt mounting and redirect to the specified path.

  By combining resolver_user/1 and resolve_access/1 callbacks it’s possible to build an authentication solution around the dashboard. For example, this resolver extracts the current_user from the conn’s assigns map and then scopes their access based on role. If it is a standard user or nil then they’re redirected to /login when the dashboard mounts.

  defmodule MyApp.Resolver do
    @behaviour Oban.Web.Resolver
  
    @impl true
    def resolve_user(conn) do
      conn.assigns.current_user
    end
  
    @impl true
    def resolve_access(user) do
      case user do
        %{admin?: true} -> :all
        %{staff?: true} -> :read_only
        _ -> {:forbidden, "/login"}
      end
    end
  end
  

• [Jobs] Change default sort direction for completed states

  Completed, cancelled, and discarded states used an unintuitive sort preference with oldest jobs first. Now it’s restored to the historic ( and more intuitive) order of newest jobs first.

• [Deps] Loosen constraints to allow Phoenix LiveView v0.20 and above

• [Deps] Require a minimum of Oban Met v0.1.2 and above

Bug Fixes

• [Chart] Correct count estimation for values between 1k and 10k

• [Job Details] Make detail times relative on demand.

  Job details always showed - because the old relative_ timestamp fields were removed. Now details show the correct relative timestamp, including a fix to correctly show the timing and duration for completed jobs.

• [Chart] Use sum for exec counts and max for full counts to display accurate information when rolling up values by periods greater than 1s. Previously, full counts were summed across time windows.

v2.10.0-rc.2 — 2023-08-22

Let’s try this one more time…

• [Assets] Inline assets and track them as external resources rather than loading on them at runtime.

v2.10.0-rc.1 — 2023-08-22

Bug Fixes

• [Assets] Correctly resolve assets directory across all build environments.

  A change to loading assets dynamically at runtime broke path resolution in release builds.