cynicollision / brewkeeper-1 Goto Github PK

probably will always be the same as "brewed on" date

e.g. /api/brew/ instead of /api/brews/, same for recipes

Default name should be "(RecipeName) batch #(TimesRecipeBrewed)"

Will need Recipe service to be able to retrieve how many times a recipe has been brewed

Store IDs/labels for brew status options

For use on recipe page and for populating default brew name

Set ownerId, get name, description, tages, source name, source url

mongod --dbpath C:\mongodata

So it doesn't have to be retrieved every single time for viewing/editing/deleting, etc... Basically just single-instance cache. Alternatively just implement full brew cache (better)

Controllers will do a Brew.getActiveBrew() to get it

They should be able to be submitted empty when no date is given

TypeError: Cannot read property 'reason' of null
at Brew.js:55
at processQueue (angular.js:13292)
at angular.js:13308
at Scope.$get.Scope.$eval (angular.js:14547)
at Scope.$get.Scope.$digest (angular.js:14363)
at Scope.$get.Scope.$apply (angular.js:14652)
at done (angular.js:9734)
at completeRequest (angular.js:9924)
at XMLHttpRequest.requestError (angular.js:9875)

User's brews will be /brews/user/:id or just the default /brews/

Limit to 10(?) and show "show more" link to retrieve all

Alternative: pages?

Instead of getting all again on brew detail page and doing linear search.
Server side looks like it is done and not being used.

Need to get current user's recipes from the Recipe service

number of brews, number of recipes, brewing since, etc

It just don't.

E.g. recipe name already in use, "not authorized" messages, required fields on mongoose Models

So I stop freaking out when suddenly something seems to have broken (e.g. user log-in) but its only because the database is offline

Set to -1 to mean "no recipe", don't bother trying to get the recipe (results in 404 currently)

• Remove recipe from brew list to make more room
• Remove filters from lists
• Replace "Add" with icon on lists
• Center recipe/brew details, center edit/delete buttons fixed below and separate

Current work around is function sanitizeUndefinedBrewValues in brew controller on server side

should not return hashed_pwd and salt to UI

For example, when adding a brew and using a bogus date value.

Use Bootstrap "alerts": http://getbootstrap.com/components/#alerts

Might be able to stick it in index.jade

mvIdentity's currentUser property is not being set correctly during log-in. It works when the page is refreshed because the window's boostrappedUser is defined.

Split send into get and post, eliminate ugly switch statement

https://bootstrap-datepicker.readthedocs.org/en/latest/

Use on the "edit brew form"

Show brews "active" brews (i.e. not "gone"), sorted by state, with their bottle/chill dates listed

Brew list: show status description instead of value

View brew: Show recipe name, link to view it

Results in "403 not authorized" errors when creating a recipe/brew because the ownerId for the new recipe isn't set correctly

If logged in as the user that added the brew, display edit/delete functionality. Also enforce on the server to only allow creator to edit/delete.

Subtle, but a UI bug nonetheless

redirect somewhere