There is an issue with refined strings not matching their regexes correctly. This could probably be solved by escaping the regex correctly. However, after discussing it, decided it would be better to not do this field-by-field validation of requests and responses. It makes the API awkward to use, and is unusual for a client stub to do this anyway, since the AWS services themselves validate their inputs.
Remove the refined Int and String types, and replace with plain Ints and Strings.
To achieve this:
- Add options to the Elm.Lang code generation module in Salix. It should be an L3 processor.
- Use the same options in the Elm.Json.Coding module.
- Make these options common to the above processors.
By doing the above, the use of refined types becomes a parameter of the code generator - can put it back at a later date if desired. Or possible validate responses, but not requests, etc.
There is an issue with refined strings not matching their regexes correctly. This could probably be solved by escaping the regex correctly. However, after discussing it, decided it would be better to not do this field-by-field validation of requests and responses. It makes the API awkward to use, and is unusual for a client stub to do this anyway, since the AWS services themselves validate their inputs.
Remove the refined Int and String types, and replace with plain Ints and Strings.
To achieve this:
By doing the above, the use of refined types becomes a parameter of the code generator - can put it back at a later date if desired. Or possible validate responses, but not requests, etc.