dklassen / chamba Goto Github PK

We are running the entire user object in the signup response need to prune back to just essential.

Implement middleware for improved logging of requests

Update the readme to provide the proper instructions for setup including Heroku and CircleCI.

Had a chat with @stevemines about UI code and where it should live. After living in both worlds for a bit decided its best to keep as much of the UI code within in the storyboard itself. We can revisit this later but the reason for this is it makes it easier for external developers to modify the storyboard and make updates which show up in the preview. I feel strongly about one place for changes either all in the UI or all in the storyboard. I don't think theres a good enough reason for allowing a split unless there is no other way of making the UI change. This is a tracking issue to make sure we convert all the existing code that lives in the classes into the storyboard.

@luccast