saltedseacorn / ctd_inventory_tracker Goto Github PK

After logging in, I can create a new inventory item

Currently the items are shown on a separate page.

Do we want to instead have our items shown on our dashboard? I think this is more direct and probably makes more sense. What are ya'lls thoughts?

Would be nice if we could upgrade our code to production by sending it to a cloud platform like Heroku!

Doesn't have to be Heroku but having our code hosted somewhere on the cloud would be really beneficial for us, don't you think?

We could use a pull request template so that we can standardize the sort of information we want to include on each pull request.

A Home page has an option to log in or create an account

We want to work in appropriate branches so I will be requested that we enable branch protection for main

Things we could include: Rails version, how to install, purpose of the app...

Create a DB schema to reflect our database and then include the DB schema into our README for great documentation!

We need to implement SimpleCov in order to generate coverage reports for out test coverage.

After running rails generate rspec:install and our Rspec files become installed, include the following in our newly created rails_helper.rb file:

require 'simplecov'
SimpleCov.start

After we will add the following lines in our .gitignore file:

/coverage.data
/coverage/*

So that our coverage reports are not tracked by Git.

We want a feature in which an email is sent to a user if an inventory item reaches zero.

We also want to consider if we will allow for negative quantities for our inventory items.

We need to run rails webpacker:install when we install a fresh copy of our application, otherwise we run into a webpacker issue.

This needs to be documented in our README at the very least.

As it stands, our Rails application looks a little plain. Functionality appears to be fine but a little bit of spice never hurts! (In moderation, of course)

So let's implement Bootstrap and see what changes in design cues we can initiate.

When we implemented rails g scaffold of our User and Items a variety of tests were created for our convenience. Those tests have not been tested and written to pass.

It should also be noted that we did not necessarily follow a TDD format for development of this application due to how we utilized rails g scaffold.

gem 'pry'
gem 'rspec-rails'

:development, :test block:

  gem 'factory_bot_rails'
  gem 'faker'
  gem 'launchy'
  gem 'simplecov'
  gem 'shoulda-matchers'

At the bottom of our rails_helper.rb file, we need to implement Shoulda-matchers.

Implementing the following code at the bottom of our rails_helper.rb file should suffice.

	Shoulda::Matchers.configure do |config|
		config.integrate do |with|
			with.test_framework :rspec
			with.library :rails
		end
	end

I can create a new user with an email and a password

We need to validate:

Presence of email
Presence of password
Uniqueness of email

And the relationship that a user has many notes items

We need to validate:

Presence of name
Presence of quantity
Numericality of quantity

Relationship: An item belongs to a user