Auth in example app needs all users' required attributes

Currently when a request to /users/login is made in the social-network example all notNullable attributes must be there or Lux will reject the request due to missing attributes. This is not the expected behaviour when authenticating with, say, an email and password.

Could be fixed in multiple ways of course:

1. Update the example to use basic auth via headers
2. Think of a solution within Lux to allow for missing data in some cases

[zacharygolba]

I was referring to using the meta property for the request however, that would still require whitelisting via the Controller#query array. Let me think about this one for a bit. I can’t determine if this is a bug or a gap in the API.

[nickschot]

I have “bypassed” this by creating a separate (model-less) auth controller. I might update the social-network example in lux-jwt to reflect this change as I think it’s a good one. This way all auth stuff like token refresh is accessible via /auth/* and is also easier/more transparently excludable from auth with lux-unless.