Space - Kate

.browserslistrc

@@ -0,0 +1 @@
+defaults

.github/PULL_REQUEST_TEMPLATE

@@ -4,10 +4,10 @@ Congratulations! You're submitting your assignment!
 ## Comprehension Questions
 Question | Answer
 :------------- | :-------------
-Describe in your own words what the Model is doing in Rails | 
-Describe in your own words what the Controller is doing in Rails | 
-Describe in your own words what the View is doing in Rails | 
-Describe an edge-case controller test you wrote |
-What is the purpose of using strong params? (i.e. the params method in the controller) | 
-How are Rails migrations related to Rails models? | 
-Describe one area of Rails that are still unclear on | 
+Describe in your own words what the Model is doing in Rails | The model interacts with the database and knows the attributes of the data. It is similar to classes in Ruby. |
+Describe in your own words what the Controller is doing in Rails | Controller is the central manager, taking in requests from the server, pulling in information from the data model, makes decisions, and hands information back to the view to render something back on the screen to the user. |
+Describe in your own words what the View is doing in Rails | The views is where the html.erb files live. The ERB is a preprocessor and evaluates any Ruby expressions before sending to the browser. The View also handles the index.html which gets sent to the browser which is the view template. |
+Describe an edge-case controller test you wrote | When the page was suppose to redirect to the main page after creating a new task.|
+What is the purpose of using strong params? (i.e. the params method in the controller) | Strong params are used in controllers to make sure that users can't update sensitive model attributes. Strong params requires the use of explicit access to attributes that we can pass onto the model methods. |
+How are Rails migrations related to Rails models? | Migrations are structured changes that can be made to a database schema. The schema is empty and lives in the model, the migration modifies it. |
+Describe one area of Rails that are still unclear on | Not really sure...|

.gitignore

@@ -1,41 +1,36 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/spec/reports/
-/test/tmp/
-/test/version_tmp/
+# See https://help.github.com/articles/ignoring-files for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile '~/.gitignore_global'
+
+# Ignore bundler config.
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+/db/*.sqlite3-journal
+/db/*.sqlite3-*
 
 # Ignore all logfiles and tempfiles.
 /log/*
 /tmp/*
 !/log/.keep
 !/tmp/.keep
 
-## Specific to RubyMotion:
-.dat*
-.repl_history
-build/
-
-## Documentation cache and generated files:
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
+# Ignore uploaded files in development.
+/storage/*
+!/storage/.keep
 
-## Environment normalisation:
-/.bundle/
-/vendor/bundle
-/lib/bundler/man/
+/public/assets
+.byebug_history
 
-# for a library or gem, you might want to ignore these files since the code is
-# intended to run in multiple environments; otherwise, check them in:
-# Gemfile.lock
-# .ruby-version
-# .ruby-gemset
+# Ignore master key for decrypting credentials and more.
+/config/master.key
 
-# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
-.rvmrc
-.DS_Store
+/public/packs
+/public/packs-test
+/node_modules
+/yarn-error.log
+yarn-debug.log*
+.yarn-integrity

.ruby-version

@@ -0,0 +1 @@
+2.6.5

Gemfile

@@ -0,0 +1,103 @@
+source 'https://rubygems.org'
+git_source(:github) { |repo| "https://github.com/#{repo}.git" }
+
+ruby '2.6.5'
+
+# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
+gem 'rails', '~> 6.0.2', '>= 6.0.2.2'
+# Use sqlite3 as the database for Active Record
+gem 'sqlite3', '~> 1.4'
+# Use Puma as the app server
+gem 'puma', '~> 4.1'
+# Use SCSS for stylesheets
+gem 'sass-rails', '>= 6'
+# Transpile app-like JavaScript. Read more: https://github.com/rails/webpacker
+gem 'webpacker', '~> 4.0'
+# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
+gem 'turbolinks', '~> 5'
+# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
+gem 'jbuilder', '~> 2.7'
+# Use Redis adapter to run Action Cable in production
+# gem 'redis', '~> 4.0'
+# Use Active Model has_secure_password
+# gem 'bcrypt', '~> 3.1.7'
+
+# Use Active Storage variant
+# gem 'image_processing', '~> 1.2'
+
+# Reduces boot times through caching; required in config/boot.rb
+gem 'bootsnap', '>= 1.4.2', require: false
+
+group :development, :test do
+  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
+  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
+end
+
+group :development do
+  # Access an interactive console on exception pages or by calling 'console' anywhere in the code.
+  gem 'web-console', '>= 3.3.0'
+  gem 'listen', '>= 3.0.5', '< 3.2'
+  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
+  gem 'spring'
+  gem 'spring-watcher-listen', '~> 2.0.0'
+end
+
+group :test do
+  # Adds support for Capybara system testing and selenium driver
+  gem 'capybara', '>= 2.15'
+  gem 'selenium-webdriver'
+  # Easy installation and use of web drivers to run system tests with browsers
+  gem 'webdrivers'
+end
+
+# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
+gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
+
+gem 'jquery-rails'
+gem 'jquery-turbolinks'
+gem 'bootstrap', '~> 4.3.1'
+group :development, :test do
+  gem 'pry-rails'
+end
+
+group :development do
+  gem 'debase', '>= 0.2.4.1'
+  gem 'ruby-debug-ide', '>= 0.7.0'
+end
+
+group :development do
+  gem 'better_errors'
+  gem 'binding_of_caller'
+  gem 'guard'
+  gem 'guard-minitest'
+end
+
+group :test do
+  gem 'minitest-rails'
+  gem 'minitest-reporters'
+end
+
+
+group :development, :test do
+end
+
+group :development do
+end
+
+group :development do
+end
+
+group :test do
+end
+
+group :development, :test do
+end
+
+group :development do
+end
+
+group :development do
+end
+
+group :test do
+end