Git it little shop of horrors movie#
Git it little shop of horrors code#
Git it little shop of horrors free#

However, it's rare in a real production system to ever truly delete content, and instead we typically just 'enable' or 'disable' content. In the user stories, we talk about 'CRUD' functionality. 'cancelled' only 'pending' and 'processing' orders can be cancelled.'complete' means all merchants have fulfilled their items for the order.'processing' means one or more merchants have fulfilled items from the order.'pending' means a user has placed items in a cart and 'checked out', but no merchant had fulfilled any items yet.Admin User - a registered user (but cannot also be a merchant) who has 'superuser' access to all areas of the application user is logged in to perform their work.Merchant User - a registered user who is also has access to merchant data and operations user is logged in to perform their work.Registered User - this user is registered and logged in to the application while performing their work can place items in a cart and create an order.Visitor - this type of user is anonymously browsing our site and is not logged in.if there is a specific gem you'd like to use in the project, please get permission from your instructors first.do not use JavaScript for pagination or sorting controls.use 'rails generators' to speed up your app development.use FactoryBot to speed up your test development.must include a thorough README to describe their project.

Git it little shop of horrors code#

must use good GitHub branching, team code reviews via GitHub comments, and use of a project planning tool like waffle.io.all controller and model code must be tested via feature tests and model tests, respectively.

Git it little shop of horrors free#

If you'd like to take a live look, please visit: Setupĭo you see changes you'd like to make? Please feel free to fork and clone our repository: ĭon't forget to bundle install/update & run your migrations in order to get the most up-to-date seed data. We used RSpec for testing and kept track of our test coverage through SimpleCov Access We used enums in our Models and before_actions in our Controllers to help us easily identify and authorize our clients. Some of the requirements surrounding this functionality are listed below in Visitor Roles.

This is an example of some of what we put together:ĭef initialize(input_data = input_data || Hash.new It took some concentration however, we're pleased with our route names and authorization game plan.

Authentication, Authorization, separation of user roles and permissions.

Session management and use of POROs for shopping cart.

Average HTML/CSS layout and design for UX/UI.

Advanced ActiveRecord for calculating statistics.

Advanced Rails routing (nested resources and namespacing).

Git it little shop of horrors movie#

Our hope is that when we're all successful developers one day, we'll have a movie marathon and watch the original and the musical version from 1986 back-to-back.

So that sequence isn't exactly what inspires us, but we did use the premise of this 1960s film to develop our quaint, creepy, little shop. Gravis Mushnik: 'And the owner got rich?'īurson Fouch: 'No, he scratched himself to death in an insane asylum.' People came from miles around to look at that wall and they stayed to buy.' Our Inspirationīurson Fouch: 'I remember in one flower shop there was a whole wall covered with poison ivy. Merchant users can mark items as 'fulfilled,' and Admin users can mark orders as 'complete.' Each user role has access to some or all CRUD functionality for application models. 'Little Shop of Orders' is a fictitious e-commerce platform where users can register to place items into a shopping cart and checkout. Contributors: Nico, Ricardo, Leah, & Tony Background and Description