Currently, if a tada event is passed parameters with more keys than a spec defines, it silently drops those extra keys (using spec-tools' coercion). This is fine, because it helps avoid potential security issues (similar to how Rails controllers handle parameters). However, in development, this can be confusing.
Suggestion:
- in development, return an appropriate anomaly and warning message for extra keys
- consider whether the error message should be different in production
Currently, if a tada event is passed parameters with more keys than a spec defines, it silently drops those extra keys (using spec-tools' coercion). This is fine, because it helps avoid potential security issues (similar to how Rails controllers handle parameters). However, in development, this can be confusing.
Suggestion: