Team LPR (Logan, Patrick, Rig) - Futbol Project Submission

Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gem 'simplecov',  require: false, group: :test

README.md

@@ -1,3 +1,73 @@
-# Futbol
+# Futbol Project - Team LPR
+
+Repository for the Team LPR version of the [Turing School](https://turing.edu/) Futbol project. 
+
+Team LPR Members:
+---------------------------------
+Patrick Little
+
+Logan Sauer
+
+Rig Freyr
+
+---------------------------------
+- Check-Ins
+----------------------------------
+We are planning on having scheduled check-ins at 2:00 pm MST on Tuesday the 14th and Friday the 17th, as well as at 11:00 am on Monday the 20th. However, we also plan to check-in on a more continuous and less formal basis throughout the development of the project.
+
+-----------------------------------
+- Project Organization and Workflow
+-----------------------------------
+Our primary vehicle for collaboration will be through GitHub; specifically, developing parallel branches of the same project repository in tandem and merging them when necessary. All merges will be handled as a group; no group member will merge their own pull requests. All group efforts and responsibilites will be tracked through a Miro board (link:https://miro.com/app/board/uXjVLuMoXq0=/) and jointly updated throughout the development process. The main body of the project can be broken into Game, League, and Season statistics methods; the team will attempt to complete one of these three categories of instanced methods collaboratavely each day.
+
+----------------------------------
+- How we made a decision on Project Organization
+-----------------------------------
+We discussed learning the usage of GitHub Projects to coordinate our work in this project, but decided it was too steep of an additional learning curve to manage for our first group development effort. Miro seemed like an efficient and easy to use alternative that we could all learn to use asynchronously in a short amount of time.
+
+
+----------------------------------
+- Approach to Code Design
+----------------------------------
+In addition to the required StatTracker class, we will need Team, Game, and Season classes to handle manipulation and sorting of the underlying CSV data for us. We will start by divying up the required Game Statistics Methods between the three of us and working on them asynchronously, so that each team member only has two or three methods to complete each day. On the next day, we will repeat this process with the League Statistics methods, and then once more with the Season Statistics on the day after that.
+
+-----------------------------------
+Initial DTR Doc Link:
+-----------------------------------
+https://docs.google.com/document/d/1ooIWGVt1z2ep9oW6uYpbnLjC3UoshCzuDN0YrBzbF_g/edit?pli=1&tab=t.0
+
+----------------------------------
+Contributors
+----------------------------------
+
+Patrick Little
+Github profile link: https://github.com/little-Patrick
+
+Rig Freyr
+Github profile link: https://github.com/ontruster74
+
+Logan Sauer
+Github profile link: https://github.com/ldsauer
+
+------------------------------------
+Iteration 3 Retrospective 
+------------------------------------
+
+For our retro, we used the EasyRetro online tool: https://easyretro.io/publicboard/bfWsAYUml2aXrJCv72tOrW7ybsM2/705879bf-e1ad-48ea-8c4f-391b64eb8ccb
+
+3 Things That Went Well During The Project
+-----------------------------------------------
+1 (Logan): I think we did a great job of staying in communication with each other and making sure that we were all on the same page as far as working through the iterations at a good pace as a group.
+
+2 (Patrick): I feel that the integration between methods and testing went a lot smoother than I expected. We had conflicts when merging to main, but it was mostly formatting issues. I like that we came together during the pull requests to do a little more live code eval, and worked through it together.
+
+3 (Rig): The team did a great job of balancing both their synchronous and asynchronous efforts. In other words, I felt like I was able to make my own schedule during the project while still working closely with everyone else involved.
+
+3 Things We Would Do Differently Next Time
+--------------------------------------------------
+1 (Logan): Take the initiative to host a "group work session" where I set up a huddle/zoom and work in there, even if it's cameras off. We talked about doing it at the beginning but I never followed through with it. So taking the initiative to set up the meeting and not wait for someone else to set it up.
+
+2 (Patrick): In the future, I want to be more communicative of what and when I am working on stuff, so if I need to reach out for help it might be easier for others to help. And vice versa, if someone needs help it is easier for them to coordinate with me.
+
+3 (Rig): It will be a good idea to slow down and review my code more carefully as I am writing it; good code is better than fast code. I will try to make my branches smaller in scope and plan their creation in advance so that they are easier to review with the group as a whole.
 
-Starter repository for the [Turing School](https://turing.edu/) Futbol project.

lib/.keep

@@ -0,0 +1,6 @@
+
+
+
+
+
+

lib/game.rb

@@ -0,0 +1,16 @@
+class Game
+  attr_reader :game_id, :season, :type, :date_time, :away_team_id, :home_team_id, :away_goals, :home_goals, :venue, :venue_link
+
+  def initialize(game_id, season, type, date_time, away_team_id, home_team_id, away_goals, home_goals, venue, venue_link)
+    @game_id = game_id
+    @season = season
+    @type = type
+    @date_time = date_time
+    @away_team_id = away_team_id
+    @home_team_id = home_team_id
+    @away_goals = away_goals
+    @home_goals = home_goals
+    @venue = venue
+    @venue_link = venue_link
+  end
+end

lib/game_factory.rb

@@ -0,0 +1,9 @@
+class GameFactory
+  def self.create_games(filepath)
+    games = []
+    CSV.foreach(filepath, headers: true, header_converters: :symbol) do |row|
+      games << Game.new(row[:game_id], row[:season], row[:type], row[:date_time], row[:away_team_id], row[:home_team_id], row[:away_goals].to_i, row[:home_goals].to_i, row[:venue], row[:venue_link])
+    end
+    return games
+  end
+end

lib/game_team.rb

@@ -0,0 +1,23 @@
+class GameTeam 
+  attr_reader :game_id, :team_id, :hoa, :result, :settled_in, :head_coach, :goals, :shots, :tackles, :pim, :power_play_opportunities, :power_play_goals, :face_off_win_percentage, :giveaways, :takeaways
+
+  def initialize(game_id, team_id, hoa, result, settled_in, head_coach, goals, shots, tackles, pim, power_play_opportunities, power_play_goals, face_off_win_percentage, giveaways, takeaways)
+    @game_id = game_id
+    @team_id = team_id
+    @hoa = hoa
+    @result = result
+    @settled_in = settled_in
+    @head_coach = head_coach
+    @goals = goals
+    @shots = shots
+    @tackles = tackles
+    @pim = pim
+    @power_play_opportunities = power_play_opportunities
+    @power_play_goals = power_play_goals
+    @face_off_win_percentage = face_off_win_percentage
+    @giveaways = giveaways
+    @takeaways = takeaways
+  end
+end
+
+

lib/game_team_factory.rb

@@ -0,0 +1,10 @@
+class GameTeamFactory 
+  def self.create_game_teams(filepath)
+    game_teams = []
+    CSV.foreach(filepath, headers: true, header_converters: :symbol) do |row|
+      game_teams << GameTeam.new(row[:game_id], row[:team_id], row[:hoa], row[:result], row[:settled_in], row[:head_coach], row[:goals].to_i, row[:shots].to_i, row[:tackles].to_i, row[:pim].to_i, row[:powerPlayOpportunities].to_i, row[:powerPlayGoals].to_i, row[:faceOffWinPercentage].to_i, row[:giveaways].to_i, row[:takeaways].to_i) 
+    end
+    return game_teams
+  end
+end
+