ash/test/type
Riccardo Binetti 23055f0a18
feat: allow providing descriptions to Ash.Type.Enum values (#940)
As discussed in https://github.com/ash-project/ash_graphql/issues/116, this
allows extensions to use the description to use the provided descriptions.

The documentation assumes that if a user provides a description, it does so for
all values (since this seems to be a reasonable assumption and allows the nicer
keyword list syntax). However tests also cover an enum with some missing
descriptions.
2024-03-22 02:38:59 -04:00
..
ci_string_test.exs improvement: add api option to relationships 2022-04-04 01:48:37 -04:00
enum_test.exs feat: allow providing descriptions to Ash.Type.Enum values (#940) 2024-03-22 02:38:59 -04:00
keyword_test.exs fix: only put keywords to be interpolated in message in error vars (#821) 2024-01-08 18:08:17 -05:00
map_test.exs fix: only put keywords to be interpolated in message in error vars (#821) 2024-01-08 18:08:17 -05:00
module_test.exs improvement: lay the groundwork for fully atomic actions 2023-12-16 10:14:02 -05:00
naive_datetime_test.exs improvement: lay the groundwork for fully atomic actions 2023-12-16 10:14:02 -05:00
new_type_test.exs improvement: add Ash.Type.NewType 2023-03-13 17:44:27 -04:00
string_test.exs improvement: lay the groundwork for fully atomic actions 2023-12-16 10:14:02 -05:00
time_test.exs improvement: lay the groundwork for fully atomic actions 2023-12-16 10:14:02 -05:00
type_test.exs improvement: lay the groundwork for fully atomic actions 2023-12-16 10:14:02 -05:00
union_test.exs test: reproduce bug casting embedded union arguments (#803) 2023-12-14 09:04:56 -05:00
uuid_test.exs fix: incorrect error for casting binary UUID (#653) 2023-07-11 20:35:01 -04:00
vector_test.exs fix: don't double-encode vector data (#934) 2024-03-20 16:32:45 -04:00