# `Localize.DateTimeParseLengthError`
[🔗](https://github.com/elixir-localize/localize/blob/v1.4.0/lib/localize/exception/date_time_parse_length_error.ex#L1)

Returned when text offered to the date-time parser is longer than a date
and time can be.

Reading a date and time means trying each place the text could divide into
a date half and a time half, so the work grows with the square of the
text's length: text that holds a hundred possible divisions is read a
hundred times over. A date and time is bounded — the longest any locale
writes, a full Dzongkha date and time with its zone named in full, is 329
bytes — so text well beyond that is refused rather than read.

The bound is 1,024 bytes and `:max_parse_length` raises or lowers it:

    config :localize, :max_parse_length, 4_096

### Fields

* `:input_length` — the length of the text offered, in bytes.

* `:max_length` — the bound it exceeded, in bytes.

# `t`

```elixir
@type t() :: %Localize.DateTimeParseLengthError{
  __exception__: term(),
  input_length: non_neg_integer() | nil,
  max_length: pos_integer() | nil
}
```

---

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