-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ship It API; #8
base: master
Are you sure you want to change the base?
Ship It API; #8
Conversation
Prepared for receiving params
…s more descriptive;
@@ -1,73 +1,24 @@ | |||
*.gem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Audrey and Vans are commenting on this one
@@ -0,0 +1,28 @@ | |||
== README |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big deal, but it's generally a good idea to update the README :)
Great job on this project, especially with the test coverage! One more thing: some of the commit messages are a bit vague-- it will definitely help in the long run if the messages are a bit more specific :) |
number_of_packages = (number_of_items / 4.0).ceil | ||
packages = [] | ||
number_of_packages.times do | ||
packages << ActiveShipping::Package.new(7, [15, 10, 4.5], units: :imperial) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
by not getting too caught up in details like package dimensions, you ended up with more time to implement tests and other cool stuff. nice project management!
@Dreedle @brittanykohler I know it's been a couple weeks, but thank you for reviewing this! I appreciate the reminders and tips. |
Ania Gonzalez & Sophia Baldonado
api site (nothing web facing): http://ship-it-api.herokuapp.com/
betsy site: http://ditzyplus.herokuapp.com/
betsy code: pottery123/betsy#2
This project was very interesting because we had a lot of conversations about what a real API would do in situations and who would have the responsibility for things, for instance, should the consumer be responsible for providing quality data? should we do some normalization and sanitation on the API end? Should we verify data formats before even trying to make a call to the shipping APIs? Lots of other good conversations. We are proud of the many validations we have. We created separate methods in the controller to handle data validations and status codes. We send different more specific statuses for different types of errors and we tried to give good responses so the consumer knows why their requests are failing or succeeding. We also got our tests to cover >95% of controllers and models which is awesome!