component

0.2.1

0.2.5 0.2.4 0.2.3 0.2.2 0.2.1 0.2.0 0.1.0

The component framework is meant to make it easy to decompose an application into many simple services. It does this by eliminating boilerplate code in common service patterns: source files can be just domain logic. See the GitHub repo for details.

HexDocs

Current section

Files

Jump to

Readme 7 Versions 2 Dependencies Dependants Files Activity

component lib component.ex

Raw

lib/component.ex

defmodule Component do

  @doc !"""
  This is the name of the function we inject into every component.
  It is used to flag the fact that a module is a component,
  and also to return metadata about that component.
  """
  def info_function_name do
    :oɟuı_ʇuǝuodɯoɔ
  end

end

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".