akoutmos/pharams

Parameter validation for Elixir Phoenix Framework

pharams's Issues

Add tests

Setup an example phoenix project which will act as the test suite for pharams

Specify param key type

Allow the developer to specify whether they want the validated/cast param keys to be atoms or strings. This is useful to ensure that pharams can be used as a drop in replacement to an existing endpoint without much refactoring and also to ensure that logging plugs are not impacted by the change (like when using config :phoenix, :filter_parameters)

Setup Travis

Setup Travis for this project so that PRs and commits can be validated

Alias fails to resolve in validate_* functions

When using an alias in the validation optional like format: SomeModule.shared_regex() the alias fails to resolve.

Making compiler errors friendly

Some of the macro errors are a little cryptic and makes it hard to know what you did wrong when using Pharams. Add some error checking and messaging to make things easier.

Aliases break when used in required/optional statements

When using an alias to define a type (for example when using exnumerator), or using calling an aliased module function the macro fails.