New spec is specific to keys in requests being strings

[grant-zukowski-xumo]

For example:

https://github.com/aws-beam/aws-elixir/blob/master/lib/aws/generated/media_package_v2.ex#L592

When building request input within Elixir, most of our codebase does it using atoms as strings:

input = %{Foo: bar}

The new spec demands that

@type create_channel_request() :: %{String.t() => any()}

@typedoc """

Example:

  filter_configuration() :: %{
    "End" => [non_neg_integer()],
    "ManifestFilter" => [String.t()],
    "Start" => [non_neg_integer()],
    "TimeDelaySeconds" => [integer()]
  }

"""

Is it possible to have the generator accept atoms as keys as well?

[onno-vos-dev]

@grant-zukowski-xumo Sorry to ignore this issue for so long 😢 I'll have a look at the codegen this weekend and see what can be done 👍 I guess this works with atoms due to to_string/1 usage in xml.ex and util.ex in which case it very much makes sense to align the spec with it 👍