Packages

use_case

0.1.9

0.2.2 0.2.1 0.2.0 0.1.9 0.1.8 0.1.7 0.1.6 0.1.5 0.1.4 0.1.3 0.1.2 0.1.1 0.1.0

A way to increase Elixir projects readability and maintenance based on Use Cases and Interactors.

HexDocs

Current section

Files

Jump to

Readme 13 Versions 0 Dependencies Dependants Files Activity

use_case priv templates use_case.gen.phx_resource_html edit.html.eex

Raw

priv/templates/use_case.gen.phx_resource_html/edit.html.eex

<h1><%%= gettext("Edit <%= @schema.human_singular %>") %></h1>

<%%= render "form.html", Map.put(assigns, :action, Routes.<%= @schema.route_helper %>_path(@conn, :update, @<%= @schema.singular %>)) %>

<span><%%= link gettext("Back"), to: Routes.<%= @schema.route_helper %>_path(@conn, :index) %></span>

Search filters

Type any of these into the search box. They can be combined with free text which searches package names and descriptions.

Operator	Description	Example
name:	Match package name. Supports * wildcards and repo/package form	name:phx* or name:hexpm/phoenix
description:	Full-text search of package descriptions	description:auth
depends:	Packages depending on a given package. Supports repo:package form	depends:ecto or depends:hexpm:ecto
build_tool:	Filter by build tool	build_tool:mix
updated_after:	Packages updated after an ISO8601 datetime	updated_after:2025-01-01T00:00:00Z
extra:	Match custom metadata (key,value). Nested keys are separated by commas	extra:license,MIT

Wrap values in double quotes to include spaces, e.g. name:"my package".