our app care about validations all the time? • View-level concern? Should form fields care about their own validity? • Client concern? Maybe delegate to the server, and screw all this nonsense! • OR, maybe we don’t fully understand what we’re building.
function() { this.validatesEmail('email'); this.validatesPresence('username'); this.validatesLength('password', { min: 6 }); this.validatesSameAs('password', 'passwordConfirmation'); } }); • Not model-based • No reliance on observers • No extending Ember or prototypes • No design choices based on reflection • No not using promises • No tests
reason, what a moran! • BUT it was an invaluable experience! • We can sort of get stuck in a bootstrapping k- hole sometimes. Common, you know it’s true. • It’s important to occasionally break out of this rut and design something; actually learn. Even if it’s just an exploration.
Here’s the code: gist.github.com/heycarsten/ 6638842 • Then, probably use something else that’s a real project, like: github.com/dockyard/ember- validations