Atoms not accepted with `string_enum_to_atom` validation

[Jdyn]

If I have

defmodule Status do
  use JSV.Schema

  def json_schema, do: string_enum_to_atom([:pending, :processing, :completed, :failed])
end

defschema(Cart, "My cart",
  status: Status,
)

shouldn't these both work:

JSV.validate(%{ "status" => :pending }, Status, []) # => {:error ... }
JSV.validate(%{ "status" => "pending" }, Status, []) # =>  {:ok, ...}

Also

defschema(Test, "datetimes",
  inserted_at: datetime(description: "Creation timestamp"),
  updated_at: datetime(description: "Last update timestamp")
)

JSV.validate(%{ "inserted_at" => ~U[2026-01-07 18:27:13.988187Z] }, Status, []) # => {:error ... }
JSV.validate(%{ "inserted_at" => "2026-01-07 18:27:13.988187Z" }, Status, []) # => {:ok ... }

I similarly to the atom example, I expect a date struct to be ok validate if the schema is datetime.

Is validate not the right thing for doing what I am trying to do? is there a better method? I feel I am trying to achieve something with this that was never intended, let me know and I can close this

[lud]

Yeah no the lib will only validate JSON-decoded form data, it's meant to be ursed at the boundaries of your system.

[Jdyn]

Yeah I am using it at the boundaries, my goal was to use it to validate the request params and my own responses against the response schemas. but my responses are from elixir land, so they have Elixir values like atoms and date structs. So validating the response boundaries are not really possible unless you essentially convert everything first, which is just extra work since Phoenix already does this at the boundary.

[lud]

If you are talking about responses from an HTTP API you can validate responses in test wiht Oaskit.Test. Otherwise yeah there would be overhead to normalize the data for validation and then encode to JSON in two steps.

[github-actions]

This issue has become stale after 7 days with no activity. Please comment or it will be closed in 7 days.