# `MishkaBlog.Blogger`
[🔗](https://github.com/mishka-group/mishka_blog/blob/v0.0.1/lib/mishka_blog/resources/blogger.ex#L5)

Manages blogger profiles in the MishkaBlog plugin with full versioning support.

This resource represents blogger profiles that are associated with users who can
create blog posts. Each blogger profile belongs to a specific site and contains
professional information including bio, expertise areas, social links, and publishing
permissions. The slug field provides a unique URL identifier for each blogger.

Blogger profiles feature full version control through PaperTrail integration, tracking
all changes with snapshot-based history and the ability to restore previous versions.
The resource implements soft deletion via archival and provides comprehensive
metadata management for public-facing blogger profiles.

Database-level constraints ensure data integrity with slug validation and prevention
of modifications to archived profiles. Multi-tenant isolation ensures blogger profiles
are properly segregated between sites. The resource provides extensive API actions
for external integrations and maintains complete audit trails of all modifications.

# `t`

```elixir
@type t() :: %MishkaBlog.Blogger{
  __lateral_join_source__: term(),
  __meta__: term(),
  __metadata__: term(),
  __order__: term(),
  aggregates: term(),
  archived_at: term(),
  author_email: term(),
  avatar_url: term(),
  bio: term(),
  calculations: term(),
  can_publish_directly: term(),
  contact_email: term(),
  cover_image_url: term(),
  display_name: term(),
  expertise_areas: term(),
  follower_count: term(),
  followers: term(),
  id: term(),
  inserted_at: term(),
  latest_version: term(),
  master_posts: term(),
  master_posts_join_assoc: term(),
  master_teams: term(),
  master_teams_join_assoc: term(),
  paper_trail_versions: term(),
  post_count: term(),
  posts: term(),
  posts_join_assoc: term(),
  recent_versions: term(),
  site: term(),
  site_id: term(),
  slug: term(),
  social_links: term(),
  sorted_versions: term(),
  teams: term(),
  teams_join_assoc: term(),
  tenant_posts: term(),
  tenant_posts_join_assoc: term(),
  tenant_teams: term(),
  tenant_teams_join_assoc: term(),
  updated_at: term(),
  user: term(),
  user_id: term(),
  version_count: term()
}
```

# `__guarded_change__`

Apply the full GuardedStruct pipeline (sanitize → validate → derive →
main_validator) to `attrs` and return either `{:ok, transformed_attrs}`
or `{:error, errors}`. Wire this into an `Ash.Resource.Change` to plug
guardedstruct rules into Ash's changeset pipeline.

The function is named `__guarded_change__` because it does more than
validate — it can also transform values (trim, downcase, slugify,
auto-fill, etc.) before they reach the data layer.

# `__guarded_field_meta__`

O(1) lookup of a field's compile-time metadata by name. Returns
`nil` for unknown fields.

# `__guarded_field_name_set__`

Compile-time-baked `MapSet` of every field name owned by the
`guardedstruct` block. Used by `GuardedStruct.AshResource.Change`
to decide, in O(1), whether a key in `changeset.atomics`
belongs to the pipeline.

# `default_short_name`

# `input`

```elixir
@spec input(values :: map() | Keyword.t()) :: map() | no_return()
```

Validates that the keys in the provided input are valid for at least one action on the resource.

Raises a KeyError error at compile time if not. This exists because generally a struct should only ever
be created by Ash as a result of a successful action. You should not be creating records manually in code,
e.g `%MyResource{value: 1, value: 2}`. Generally that is fine, but often with embedded resources it is nice
to be able to validate the keys that are being provided, e.g

```elixir
Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> Ash.create()
```

# `input`

```elixir
@spec input(values :: map() | Keyword.t(), action :: atom()) :: map() | no_return()
```

Same as `input/1`, except restricts the keys to values accepted by the action provided.

# `json_api_match_route`

# `primary_key_matches?`

---

*Consult [api-reference.md](api-reference.md) for complete listing*