Here's some reading on commit opinions. While I know for our purposes, this can, perhaps, be too verbose, I think there's some good things to think about especially as many people will work in environments with other developers, eventually.
For our Shylock project, consider how you might have gone above just writing 'Act 1,' 'Act 2,' etc. at the end of each prompted section, maybe we could break it down more. While it might seem more tedious, it helps to be explicit and specific. Instead of doing git add .
, remember that you can specify which files to add. Be more descriptive with our commit messages.
git add index.html
git commit -m 'Act 1 - added form, included scripts for xyz'
git add main.js
git commit -m 'Act 1 - working on parse prompt function'
git push origin master
Hi, y'all. I didn't see a whole lot of people taking advantage of setting key value pairs in an object to keep track of users and the amount they've been loaned. A lot of people did comparing of items in arrays, which works fine, but when you update your amount, it can get a bit out of hand since you don't take into account the same user, unless you do a lot of comparisons. Of course, this is just a skeleton of the assignment, so you have to be pretty literal. When trying to call the loan functionality, use this format:
loan abner 10 ducats
Open up the console and follow the trail of comments. I tried to make it easy to follow along. Check it out.