7.2.0 • Published 5 years ago

mcubed-lineup-insight-data v7.2.0

Weekly downloads
7
License
MIT
Repository
github
Last release
5 years ago

mcubed-lineup-insight-data

Description

This node module will retrieve fantasy sports data. In particular, this will aggregate data such as starting players, projected points, and recent performances for daily fantasy sports sites like DraftKings, FanDuel, and Yahoo.

mcubed-lineup-insight-data vs. mcubed-lineup-insight-server

mcubed-lineup-insight-server is a node module that relies on mcubed-lineup-insight-data for all of its data. The data module is used for retrieving the fantasy sports data from third-parties. The server module is used for aggregating the data for all the current contests and merging the data from the different third-parties into the contests.

Command Line Interface

This node module can be run from the command line using mcubed-lineup-insight-data -d PlayerInsight -c DraftKings -s NFL. The arguments for the command line interface are:

  • -d / --data - Optional. Specifies the type of data to retrieve. This option is case-insensitive and should be on of the DataTypes. If this argument is omitted, then PlayerInsight is used as the default value.
  • -c / --contestType - Required. Specifies the contest type to retrieve the data for. This option is case-insensitive and should be one of the ContestTypes.
  • -s / --sport - Required for PlayerInsight and TeamInsight. Specifies the sport to retrieve the data for. This option is case-insensitive and should be one of the supported Sports.
  • --contestID - Required for PlayerCard. Specifies the contest ID to get the player card for.
  • --playerID - Required for PlayerCard. Specifies the player ID to get the player card for.

When run from the command line:

  • The contest list request will produce an array of Contests written as a JSON formatted string to the standard output.
  • The player card request will produce a PlayerCard object written as a JSON formatted string to the standard output.
  • The player insight request will produce an array of Players written as a JSON formatted string to the standard output.
  • The team insight request will produce an array of TeamInsights written as a JSON formatted string to the standard output.

Node Module Dependency

This node module can be used as a dependency of another node module. Run npm install mcubed-lineup-insight-data --save to add it as a dependency to your node module. An example usage of the module:

import insightData, * as interfaces from "mcubed-lineup-insight-data";

insightData.getPlayerInsight(interfaces.ContestType.DraftKings, interfaces.Sport.NFL).then((players) => {
    players.forEach((player) => {
        console.log(player.name);
    });
});

Error Handling

Whether using this module via the Command Line Interface or as a Node Module Dependency, the error handling will be the same. All errors thrown from this module will reject the promise that is returned from the InsightData class. The errors will always be of type Error. When running from the Command Line Interface, only the message property from the Error object will be written as a JSON formatted string to the standard error output. An example output of an error on the command line would look like:

{"message":"Could not retrieve data"}

API

InsightData

An instance of this class is returned when requiring mcubed-lineup-insight-data from within a node module.

  • getContestList(contestType: ContestType, sport: Sport): Promise<Contest[]> - Returns a list of contests that are currently active for the DFS site. The contestType parameter is optional and should be a valid ContestType value. If no contestType is specified, then all contest types are returned. The sport parameter is optional and should be a valid Sport value. If no sport is specified, then all sports are returned. The return value is a promise that yields an array of Contests.
  • getPlayerCard(contestType: ContestType, contestID: string, playerID: string): Promise<PlayerCard> - Returns an object containing specific information about a single player for a contest. The contestType parameter is required and should be a valid ContestType value. The contestID parameter is required and should be an ID from a contest object from the getContestList function. The playerID parameter is required and should be an ID from a player object nested within a contest object from the getContestList function. The return value is a promise that yields a PlayerCard.
  • getPlayerInsight(contestType: ContestType, sport: Sport): Promise<Player[]> - Returns the data for a specified contest type and sport combination. The contestType parameter is required and should be a valid ContestType value. The sport parameter is required and should be a valid Sport value. The return value is a promise that yields an array of Players.
  • getTeamInsight(contestType: ContestType, sport: Sport): Promise<TeamInsight[]> - Returns the team-specific data for a specified contest type and sport combination. The contestType parameter is required and should be a valid ContestType value. The sport parameter is required and should be a valid Sport value. The return value is a promise that yields an array of TeamInsights.

Player

Instances of this class are returned from calling the getPlayerInsight function from the InsightData object or serialized to JSON when using the command line interface.

  • ID?: string - Optionally specifies a unique identifier for the player.
  • injury?: PlayerInjury - Optionally specifies Injury information for the player.
  • isStarter?: boolean - Optionally specifies if the player is in the starting lineup.
  • mlbSpecific?: PlayerMLBSpecific - Optionally specifies the PlayerMLBSpecific identifying more information about the player. This data will only exists for players participating in MLB contests.
  • name: string - Specifies the name of the player (formatted as "First Last Suffix").
  • newsStatus?: NewsStatus - Optionally specifies the NewsStatus for the player.
  • position?: string - Optionally specifies the position the player plays.
  • positionEligibility?: string[] - Optionally specifies an array of positions the player is eligible for within a given contest. For instance, a RB may be eligible for the "RB" and the "RB/WR/TE" positions. This eligibility will be more reliable than the eligiblePlayerPositions from a Contest's ContestPosition. This occurs when DFS sites run unordinary contests such as tier-based RB positions where there is a RB Tier 1 and a RB Tier 2 position available. For both of these positions, the ContestPosition will return "RB" as an eligiblePlayerPosition. However, a player is likely only truly eligible for one of the two tiers. If a RB is only available for the RB Tier 1 position, this positionEligibility array will only contain "RB Tier 1".
  • salary: number - Specifies how much the player costs for the contest.
  • stats?: PlayerStats[] - Optionally specifies an array of PlayerStats associated with the player.
  • team: string - Specifies the team abbreviation the player plays for.
  • thumbnailURL?: string - Optionally specifies a URL to a thumbnail image of the player.

PlayerMLBSpecific

Instances of this class are associated with a Player. These will only be created if the player is participating in an MLB contest.

  • battingOrder?: string - Optionally specifies the batting order of the player for an MLB contest.
  • handednessBat?: string - Optionally specifies the batting handedness of the player for an MLB contest. This will be one of R, L, or S.
  • handednessThrow?: string - Optionally specifies the throwing handedness of the player for an MLB contest. This will be one of R, L, or S.
  • isProbablePitcher?: boolean - Optionally specifies if the player is expected to be the starting pitcher for an MLB contest.

PlayerInjury

Instances of this class are associated with a Player.

  • display: string - Specifies a display value describing the injury.
  • injuryType: InjuryType - Specifies the InjuryType for the player.

PlayerStats

Instances of this class are associated with a Player.

  • source: string - Specifies the source of which the data came from.
  • projectedCeiling?: number - Optionally specifies the projected ceiling for the player.
  • projectedFloor?: number - Optionally specifies the projected floor for the player.
  • projectedPoints?: number - Optionally specifies the projected points for the player.
  • recentAveragePoints?: number - Optionally specifies the average number of points the player has scored recently.
  • seasonAveragePoints?: number - Optionally specifies the average number of points the player has scored on the season.

PlayerCard

Instances of this class are returned from calling the getPlayerCard function from the InsightData object or serialized to JSON when using the command line interface.

  • gameLog: PlayerCardGameStats[] - Specifies an array of PlayerCardGameStats containing statistics for recent performances by the player.
  • news: PlayerCardArticle[] - Specifies an array of PlayerCardArticle containing news for the player.

PlayerCardArticle

Instances of this class are associated with a PlayerCard.

  • date: Date - Specifies the date the news was published for the player.
  • details: string - Specifies the full details of the news article for the player.
  • summary: string - Specifies a summary for the news article for the player.

PlayerCardGameStats

Instances of this class are associated with a PlayerCard.

  • date: Date - Specifies the date of the performance by the player.
  • opponent: string - Specifies the opponent that the performance was against. For home performances, this will be returned as "vs. OPP". For away performances, this will be returned as "@ OPP".
  • points?: number - Optionally specifies the number of fantasy points the player received for the performance.

Contest

Instances of this class are returned from calling the getContestList function from the InsightData object or serialized to JSON when using the command line interface.

  • contestType: ContestType - Specifies the ContestType.
  • games?: Game[] - Optionally specifies an array of Games associated with the contest.
  • ID: string - Specifies a unique identifier for the contest.
  • label: string - Specifies a label describing the contest.
  • maxPlayersPerTeam?: number - Optionally specifies the maximum number of players allowed from a single team when building a lineup.
  • maxSalary?: number - Optionally specifies the maximum total salary allowed when building a lineup.
  • positions?: ContestPosition[] - Optionally specifies an array of ContestPositions representing the positions needed to fill a lineup.
  • sport: Sport - Specifies the Sport.
  • startTime?: Date - Optionally specifies the start time for the contest.

ContestPosition

Instances of this classes are associated with a Contest and represent a position needed to fulfill the contest requirements. A player may be listed for a single position, but that player may be used to fulfill any number of available positions in the contest lineup. For instance, a player listed as a RB may be eligble to fulfill a RB slot, a RB/WR/TE slot, a Util slot, an MVP slot, etc.

  • eligiblePlayerPositions: string[] - Specifies the array of positions that may be used to fulfill the player slot. For a RB/WR/TE slot, this would be an array containing "RB", "WR", and "TE".
  • label: string - Specifies the label that is listed on the contest for the player slot. For a RB/WR/TE slot, this would return "RB/WR/TE".
  • tier?: string - Optionally specifies a tier used internally for calculating the positionEligibility of a Player.

Game

Instances of this class are associated with a Contest and represent a game that will be played as part of the contest.

  • awayTeam: Team - Specifies the away Team.
  • homeTeam: Team - Specifies the home Team.
  • startTime: Date - Specifies the start time for the game.

Team

Instances of this class are associated with a Game and represent a team that will play as part of the contest.

  • code: string - Specifies the team abbreviation (e.g., "BOS").
  • fullName: Team - Specifies the full team name (e.g., "Boston Red Sox").
  • players?: Player[] - Optionally specifies an array of Players that are on the team.

TeamInsight

Instances of this class are returned from calling the getTeamInsight function from the InsightData object or serialized to JSON when using the command line interface.

  • code: string - Specifies the team abbreviation (e.g., "BOS").
  • fullName: Team - Specifies the full team name (e.g., "Boston Red Sox").
  • pointsAllowedPerPosition?: PositionPoints[] - Optionally specifies an array of PositionPoints representing the fantasy points allowed to a particular position.

PositionPoints

Instances of this class are associated with a TeamInsight and represents the number of fantasy points allowed to the opposing position. For MLB, instead of basing it on the opposing position, it is based on the opposing handedness. For points allowed to opposing hitters, the position would be one of BAT-R (right handers), BAT-L (left handers), or BAT-S (switch hitters). For points allowed to opposing pitchers, the position would be one of PITCH-R (right handers) or PITCH-L (left handers).

  • position: string - Specifies the position the points were allowed to (e.g., "QB", "RB", "PG", "SF"). For MLB, specifies the handedness the points were allowed to (e.g., "BAT-R", "BAT-L", "BAT-S", "PITCH-R", "PITCH-L").
  • points: number - Specifies the number of fantasy points allowed to the position.
  • source: string - Specifies the source of which the data came from.

ContestType

Defines an enumerated list of valid contest types. A contest type represents a DFS site.

  • DraftKings
  • FanDuel
  • Yahoo

DataType

Defines an enumerated list of valid data types. A data type represents information that may be retrieved from this module.

  • ContestList - Used to retrieve a list of contests.
  • PlayerCard - Used to retrieve detailed information about a specific player.
  • PlayerInsight - Used to retrieve projected points and other general information about all players.
  • TeamInsight - Used to retrieve general information about all teams.

InjuryType

Defines an enumerated list of valid injury types. An injury type represents the likelihood that the player will play with the injury.

  • Out
  • Possible
  • Probable

NewsStatus

Defines an enumerated list of valid news statuses. A news status represents the freshness of news on a player.

  • Breaking
  • Recent
  • None

Sport

Defines an enumerated list of valid sports supported by this module.

  • MLB
  • NBA
  • NFL
  • NHL

Developer Setup

  1. Use git clone to clone the GitHub repository
  2. In the root directory of the module, run: npm install

Versioning

This package will follow the semantic versioning (X.X.X) and will be updated as such:

  • Major releases or changes that will break the API will increment the first number. This will include renaming properties or otherwise refactoring the API.
  • New features that do not break the API will increment the middle number. This will include adding contest sites, data retrievers, sports, and additional data.
  • Bug fixes and minor changes will increment the last number. This will include maintenance efforts for the current set of contest sites, data retrievers, and sports.

Usage Notice

This node module does not formulate any of its own data. It aggregates the data formulated by third-party fantasy sports data providers. All data collected by this node module is freely available without the use of any premium subscriptions. Not all third-party providers provide data for each contest type or sport. This node module will provide the information that it can get and will correlate the data to the third-party data provider it came from. All attribution of any data that is used from this node module should be attributed to the third-party data providers.

Attribution

Thanks to the following third-parties for providing the data that makes this node module possible:

7.2.0

5 years ago

7.1.0

5 years ago

7.0.0

5 years ago

6.0.2

5 years ago

6.0.1

5 years ago

6.0.0

5 years ago

5.0.0

5 years ago

4.1.0

6 years ago

4.0.0

6 years ago

3.2.1

6 years ago

3.2.0

6 years ago

3.1.0

6 years ago

3.0.0

6 years ago

2.0.0

7 years ago

1.1.6

7 years ago

1.1.5

7 years ago

1.1.3

7 years ago

1.1.2

7 years ago

1.1.1

7 years ago

1.1.0

7 years ago

1.0.4

7 years ago

1.0.3

7 years ago

1.0.2

7 years ago

1.0.1

7 years ago

1.0.0

8 years ago

0.4.0

8 years ago

0.3.1

8 years ago

0.3.0

8 years ago

0.2.2

8 years ago

0.2.1

8 years ago

0.2.0

8 years ago

0.1.1

8 years ago

0.1.0

8 years ago

0.0.2

8 years ago

0.0.1

8 years ago