angular-parsers-formatters-validators-lab's Introduction

Parsing and displaying form data and errors

Objectives

Use $parsers, $formatters and $validators to format form Models
Use ngMessages to display relevant error messages

Instructions

In this repo we've got a sign up form. This requires the user's name, and their coupon code.

Add a directive that uses $parsers and $formatters to ensure that the coupon is always displayed in lowercase in the view, no matter what case we type in.
We also need to make sure the coupon code is correct. This should conform to the regular expression /\d{2}[a-z]{4}\d{2}/i (two digits, then 4 characters, then 2 digits). Add a directive to validate this! If there's an error with the code, it should be displayed on the view!

angular-parsers-formatters-validators-lab's People

Contributors

Watchers

angular-parsers-formatters-validators-lab's Issues

No package.json

I can't run the tests because there is no package.json file.

I think there's an inconsistency in this lab regarding whether a $formatter is required... because I don't believe it is as the specs are written even though the directions mention's including one. The solution includes a $formatter, but to make the coupon code upper case which seems unrelated to the lab's instructions. I think the directions/solution/specs could just be tweaked slightly for consistency.

$formatters not necessary

Not sure if this was intended, but only $parsers is required to pass this lab. I commented out my $formatters and everything works fine. $parsers is doing the job of the formatters since the input is being displayed immediately after being parsed. It would be pretty simple to add an element that uses $formatters for some model that isn't already being parsed for the exact same thing.