sleeper_api 1.3.0 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6fd4df8d68adb46808ea692bbf8c715f2218a07a8f93212f5efddfe404741a30
-  data.tar.gz: cd3b09acb61407c634f04d76f165a1d2e0b7b840b3564117136ecc9343bc286c
+  metadata.gz: c89b9383f35e517efd9ce353f9c14b1463f37375cc7dc4c30310c5c57370cdab
+  data.tar.gz: 336f7a25653bdbad75ec3094d150389fb5abba4244ef80ffbe97ce702e6a7ce9
 SHA512:
-  metadata.gz: a63777ce6255da38e963034bf9b016ca327d85dcaefc723ad508c85d58c9674939474ee00bd55b33b007e3268a043e81f8c175f06276cb77ae80b6a619871431
-  data.tar.gz: aed8fa84f731ddb1e8a01ef2cfb8987305826f665f338954e990fcb8c2c946c3d33f73edf510217ecee1923412bc6470a56931dbd9c60ba7369230c2c847627c
+  metadata.gz: 49c0c6f2843e597c53cf8c8c548a348f7c03255e6a38306a8e43190523f2ad485125145e9dc844b4f6b1ea326b74286e8a26cffa34c8c8522caeb70822477f0b
+  data.tar.gz: 45c2ebd6bc9b2e9ef3cd4f5f53c6635cd00f8199f9f5da7d0061d740c99f27aa94a1894ac682d072fb542e5c0498996ba799d1ee8c094689281188befdce33f3

data/CHANGELOG.md

@@ -1,3 +1,111 @@
+## [1.4.0] - 2026-09-14
+
+### Added
+
+- **`Client#stats_with_context(season, week)` — one week's stat lines carrying
+  the week they were played in.** Each row has the player's team *that week*,
+  their `opponent`, the `game_id` and the `date`, which the existing `#stats`
+  endpoint does not return at all.
+
+  ⚠️ **It is served from a different host: `api.sleeper.com`, not
+  `api.sleeper.app`.** Same sport and season in the path, no `/v1`, and the
+  season type is a query parameter rather than a segment. The `.app` endpoint
+  answers the *same stat lines with none of this metadata*, which is how it sat
+  unfound through four epics of stats work in the consuming app.
+
+  **What is genuinely per-week, measured** over the 2,275 players present in
+  both week 1 and week 16 of 2021: `team` differs on **164** of them and
+  `opponent` on **2,262**. ⚠️ **The nested `player` object is not history** — it
+  is the current catalog record stapled on, with `team` null inside it and
+  `injury_status` differing on 1 of the 204 rows carrying one across those
+  fifteen weeks. A 2021 row reporting "Questionable" is reporting that he is
+  questionable *now*.
+
+  ⚠️ **Pass a week.** Dropping it answers season totals — 8,251 rows for 2021 —
+  with `week` and `opponent` null on every one, so the season form carries none
+  of the context the endpoint exists for. Shares `#stats`' traps otherwise:
+  nothing 404s, and `pre`/`post` restart week numbering. An array of rows, not
+  a hash keyed by player id.
+
+### Changed
+
+- **`make_request` takes an optional `host:`**, which is how the second host is
+  reached. ⚠️ **Passing an absolute URL instead does not work**: HTTParty 0.24
+  raises `UnsafeURIError` for any URL whose host differs from the configured
+  `base_uri` — "this request could send credentials to an unintended server" —
+  so a second host has to arrive as its own per-request `base_uri`.
+
+  **Errors and logs now name the host whenever it is not the default.**
+  `/stats/nfl/2021/16` is a real path on both hosts and they return different
+  things, so a message quoting the path alone cannot say which one failed.
+  Messages for paths on `api.sleeper.app` are byte-for-byte what they were.
+
+## [1.3.1] - 2026-09-10
+
+### Fixed
+
+- **Every request raised `ArgumentError: unknown keyword: quirks_mode` under
+  `json` 3.0.** HTTParty 0.24.2 parses with `JSON.parse(body, quirks_mode:
+  true, allow_nan: true)`; json 3.0 removed that keyword. Total breakage rather
+  than a degradation, and it arrives through a transitive bump rather than
+  anything a consumer chose — this gem has no committed lockfile, so CI went
+  red with no commit in between. httparty 0.24.2 is the newest release and has
+  no fix.
+
+  `SleeperApi::JsonParser` subclasses `HTTParty::Parser` and overrides its
+  `json` method to drop the flag; `Client` parses with it. **Deliberately not a
+  `json < 3` pin in the gemspec**, which would fix the same crash by forbidding
+  every app that uses this gem from upgrading json at all, for a flag none of
+  them asked for.
+
+  `quirks_mode: true` allowed a bare scalar at the top level, which is not
+  academic here — Sleeper answers an unknown username with a literal `null`.
+  Both majors parse that correctly without it: `JSON.parse("null")` is `nil`
+  under 2.21.2 and under 3.0.2. The suite passes under both.
+
+### Documented
+
+Three facts measured against the live API on 2026-09-10, while NFL week 1 was
+half-played — one game finished, one being played, fourteen not yet started.
+No behaviour changed; all three are things a caller could previously only find
+out by being wrong first.
+
+- **`#schedule`'s `status` values are named: `pre_game`, `in_game`, `complete`,
+  `canceled`.** `in_game` was read off a live game; the other three come from
+  the published 2025 and 2026 schedules. It is the only per-game signal that a
+  game has been played — this payload has a `date` and no kickoff time, so a
+  caller can know a game is under way but never how far into it. **A week is
+  not one event**: week 1 of 2026 held three of those states at once, so
+  reasoning about "has the week started" from `date` alone gets it wrong for
+  everyone whose game is on Sunday. Treat the four as open and match with a
+  fallback — a postponement would be a fifth and none has been seen.
+
+- **`#projections` is a pre-game, whole-game projection that does not move
+  while the game is played.** Five players in one night's game held the same
+  `pts_ppr` to the decimal across six hours spanning its kickoff; a game that
+  had already finished still projected 19.69 for a player who scored 26.2, so
+  it does not settle onto the final either. This is the natural endpoint to
+  reach for when building anything live, and it cannot answer the question:
+  **there is no live projection here**, so nothing in this payload says whether
+  a player is on pace. A player on 8 of a projected 12 in the first quarter is
+  ahead of schedule, and this reports 12 all afternoon.
+
+- **`#stats` answers a week still being played with a partial set, and says
+  nothing about being partial.** Mid-week-1 it returned 301 rows with 42
+  carrying a `pts_ppr`. That is distinct from the already-documented empty
+  week: a caller treating "the week's stats" as the whole week gets a
+  half-filled answer for as long as the week is in progress, which for a
+  regular-season week is most of five days. `#schedule`'s per-game `status` is
+  the only thing that tells a missing row from a scoreless one.
+
+### Changed
+
+- `#schedule`'s spec fixture carries all four statuses rather than `pre_game`
+  alone, and an example pins that they pass through untranslated. The narrow
+  fixture was a shape live data produces only on a quiet Tuesday, and a fixture
+  narrower than the API is how a caller ends up written against a vocabulary of
+  one.
+
 ## [1.3.0] - 2026-08-27
 
 ### Added

data/CLAUDE.md

@@ -19,7 +19,7 @@ bundle exec rubocop -A     # autocorrect
 bin/console                # IRB with the gem loaded
 ```
 
-CI (`.github/workflows/ci.yml`) runs `bundle exec rake ci` on Ruby 3.2 only. The gemspec claims `required_ruby_version >= 2.6.0` and RuboCop targets 2.6, but nothing tests below 3.2 — treat 2.6 compatibility as unverified.
+CI (`.github/workflows/ci.yml`) runs `bundle exec rake ci` on Ruby 3.2 and 3.4. The gemspec claims `required_ruby_version >= 2.6.0` and RuboCop targets 2.6, but nothing tests below 3.2 — treat 2.6 compatibility as unverified.
 
 ## Architecture
 
@@ -29,6 +29,27 @@ Four layers, with a deliberate split between HTTP and modeling:
 - **`Client`** — the only thing that talks HTTP. `include HTTParty` with `base_uri "https://api.sleeper.app"` — **the bare host; the `/v1` lives in each path**. That is deliberate and load-bearing: not every Sleeper endpoint is versioned. `/schedule/{sport}/{season_type}/{season}` is served from the host root, and while `base_uri` carried the version that endpoint was unreachable at any path a caller could pass in. A new endpoint spells out where it lives; do not move the version back into `base_uri` to shorten the paths.
 
   Every call funnels through the private `make_request`, which handles retry-on-timeout, logging, and converts non-2xx into `SleeperApi::Error`. **That error quotes the path**, so the path prefix is part of a public string — v1.2.0 changed it from `"Failed to fetch /user/x: 404"` to `"Failed to fetch /v1/user/x: 404"`. `Client` also owns the 24-hour in-memory player cache.
+
+  ⚠️ **There are two Sleeper hosts and v1.4.0 added the second.** `WEB_HOST`
+  (`https://api.sleeper.com`) is the one the web app uses, and it serves
+  **richer rows from same-looking paths**: `#stats_with_context` returns the
+  player's team *that week* and their opponent, while `#stats` on `.app`
+  returns the same stat lines with neither. Reached with `make_request(path,
+  host: WEB_HOST)` rather than by moving `base_uri`, because every other
+  endpoint lives on `.app`.
+
+  **Passing an absolute URL instead does not work**, and the failure is not
+  subtle: HTTParty 0.24 raises `UnsafeURIError` for any URL whose host differs
+  from the configured `base_uri` — *"this request could send credentials to an
+  unintended server"* — so a second host must arrive as its own per-request
+  `base_uri`. **The error and the log name the host whenever it is not the
+  default**, because `/stats/nfl/2021/16` is a real path on both and they
+  return different things; paths on `.app` quote exactly as they did before.
+
+  **When an endpoint almost has what you need, try the other host before
+  concluding the data does not exist.** Four epics of stats work in the
+  consuming app never surfaced the per-week team, because the documented-looking
+  path on `.app` answers 200 with a payload that simply omits it.
 - **`League` / `User` / `Draft`** — resource objects. Each takes `(id, client)`, fetches eagerly in the constructor, memoizes into ivars, and exposes formatted hashes.
 - **`Helpers`** — mixed into all four. `deep_symbolize_keys` plus `player_details`, which reaches through `@client` — so any class including it must define `@client`.
 
@@ -44,6 +65,22 @@ Four layers, with a deliberate split between HTTP and modeling:
 
 **Never fan out `get_players`.** It's a multi-megabyte payload of every NFL player. It's cached for 24h in an ivar on the client instance — which means the cache dies with the client. Consumers holding a short-lived client re-download it every time.
 
+### Undocumented endpoints carry undocumented vocabularies
+
+Sleeper publishes no field reference, so every enum this gem passes through was
+found by looking. Four are known — `#schedule`'s game `status`, `Player`'s
+`status` and `injury_status`, and a roster's `lineup_position` — and **none of
+them is closed**. Match with a fallback rather than a whitelist, and never
+translate one into a vocabulary of this gem's own: the caller is the only one
+who knows what to do with a value nobody has seen.
+
+**When a value is measured, name it in the docstring and put the date and the
+circumstance next to it.** `in_game` shipped as an unnamed fallback in the
+consuming app for a day before anyone saw a live game; the fallback was right,
+and the thing that made it a fact rather than a guess was writing down that it
+was read at 21:13 on 2026-09-10 during a specific game. A vocabulary with no
+provenance is indistinguishable from one somebody assumed.
+
 ## Testing
 
 RSpec + WebMock, with `WebMock.disable_net_connect!` — **specs must never hit the network**. Stub with `stub_request` (see `client_spec.rb`) or `instance_double(SleeperApi::Client)` for resource-object specs (see `league_spec.rb`).
@@ -54,6 +91,24 @@ RSpec + WebMock, with `WebMock.disable_net_connect!` — **specs must never hit
 
 `lib/` is at 100% line coverage. Every bug found in this gem so far has been in a `League#format_*` method handling a field Sleeper omitted, exercised only by real data. When adding a formatter, write the nil-field case first.
 
+### There is no committed Gemfile.lock, so CI resolves fresh every run
+
+That is right for a library — a lockfile would hide exactly the incompatibility
+a consumer is going to hit — but it has a consequence worth naming: **a green
+run does not stay green.** A transitive release can turn CI red with no commit
+in between, and the first PR opened afterwards looks like the culprit.
+
+`json` 3.0 did this on 2026-09-11. It removed `quirks_mode`, which
+`httparty` 0.24.2 passes on every JSON parse, so 11 examples began raising
+`ArgumentError: unknown keyword: quirks_mode` — on a documentation-only PR that
+touched no code. Check whether `main` is red before reading a failure as the
+branch's fault; `main`'s last run can be weeks old.
+
+`SleeperApi::JsonParser` is the fix, and it is worth reading before reaching for
+a version pin: the gem overrides the one broken method rather than constraining
+`json` in the gemspec, because a constraint there would forbid every consuming
+app from upgrading `json` for a flag none of them asked for.
+
 ## Release
 
 Version lives in `lib/sleeper_api/version.rb`. Update `CHANGELOG.md`, then `bundle exec rake release` from a clean `main`, which builds to `pkg/`, tags, pushes the tag, and uploads to rubygems.

data/lib/sleeper_api/client.rb

@@ -22,6 +22,17 @@ module SleeperApi
     # pass to make_request.
     base_uri "https://api.sleeper.app"
 
+    # ⚠️ **The other Sleeper host.** The web app talks to `api.sleeper.com`,
+    # which serves *richer rows from same-looking paths* — see
+    # #stats_with_context. Reached per-request rather than by moving base_uri,
+    # because every other endpoint here lives on `.app`.
+    WEB_HOST = "https://api.sleeper.com".freeze
+
+    # Not HTTParty's own. Its JSON branch passes `quirks_mode`, which json 3.0
+    # removed, so without this every response raises ArgumentError the moment a
+    # consumer resolves json 3. See JsonParser.
+    parser SleeperApi::JsonParser
+
     # @param config [SleeperApi::Configuration] Client configuration
     def initialize(config)
       @config = config
@@ -223,6 +234,14 @@ module SleeperApi
     # a legitimate answer and is indistinguishable from a typo. Validate the
     # arguments before you trust an empty body.
     #
+    # **A week still being played answers with a partial set, and says nothing
+    # about being partial.** Mid-week-1 of 2026 this returned 301 rows with
+    # only 42 carrying a `pts_ppr` — the two teams whose games had finished or
+    # started. A caller that treats "the week's stats" as the whole week gets a
+    # half-filled answer for as long as the week is in progress, which for a
+    # regular-season week is most of five days. #schedule's per-game `status`
+    # is the only thing that can tell a missing row from a scoreless one.
+    #
     # Omitting `week` requests season totals, which is a different resource at
     # a shorter path rather than a default of week 1.
     #
@@ -249,6 +268,20 @@ module SleeperApi
     # `adp_dd_ppr` 1000.0 and `pos_rank_*` 999.0 are "unknown" sentinels rather
     # than values.
     #
+    # ⚠️ **This is a pre-game, whole-game projection and it does not move while
+    # the game is played.** Measured on 2026-09-10 across six hours spanning a
+    # kickoff: five players in that night's game held the same `pts_ppr` before
+    # it started and while it was in progress, to the decimal. Checked again
+    # against a game that had already finished — the projection still read
+    # 19.69 for a player who had scored 26.2, so it does not settle onto the
+    # final either.
+    #
+    # That matters because it is the natural thing to reach for and the wrong
+    # one: **there is no live projection here**, so nothing in this payload can
+    # say whether a player is on pace. A player on 8 points of a projected 12
+    # in the first quarter is ahead of schedule, and this endpoint will report
+    # 12 all afternoon.
+    #
     # @param season [Integer, String] Season year, e.g. 2026
     # @param week [Integer, String, nil] Week number, or nil for season totals
     # @param season_type [String] "regular" (default), "pre", or "post"
@@ -258,6 +291,55 @@ module SleeperApi
       make_request(weekly_path("projections", sport, season_type, season, week))
     end
 
+    # Get one week's stat lines **with the context of the week they were played
+    # in** — the player's team *that week*, their opponent, the game and its
+    # date. Probed 2026-09-08, re-probed 2026-09-14.
+    #
+    # ⚠️ **A different host: `api.sleeper.com`, not `api.sleeper.app`.** The
+    # `.app` endpoint #stats calls returns the *same stat lines with none of
+    # this metadata*, which is why it can be there for years without anyone
+    # finding it. Same sport and season in the path, but no `/v1` and the
+    # season type is a query parameter rather than a segment.
+    #
+    # **What is genuinely per-week, measured** over the 2,275 players present in
+    # both week 1 and week 16 of 2021: `team` differs on **164** of them (a
+    # midseason trade is a real change of team) and `opponent` on **2,262**. So
+    # both are history rather than today's catalog.
+    #
+    # ⚠️ **The nested `player` object is NOT history.** It is the current
+    # catalog record stapled on — `player.team` is null inside it, and
+    # `injury_status` differed on 1 of the 204 rows carrying one across fifteen
+    # weeks, which is the signature of a field that does not vary by week at
+    # all. A 2021 row reporting "Questionable" is reporting that he is
+    # questionable *now*. The top-level `status` is null on every row seen.
+    #
+    # ⚠️ **Pass a week.** Dropping it answers season totals — 8,251 rows for
+    # 2021 — with `week` and `opponent` null on every one, so the season form
+    # carries none of the context this endpoint exists for.
+    #
+    # Shares #stats' traps: nothing 404s (an unplayed 2026 week, a week out of
+    # range, a season before Sleeper's history and a garbage season type all
+    # answer `200` with `[]`), and `pre`/`post` restart week numbering — 2021
+    # `post` week 1 is the wildcard round, played 2022-01-15.
+    #
+    # **An array, not a hash.** #stats keys by player id; this returns a list of
+    # rows each carrying `player_id`, so a caller indexing it must build its own
+    # map. `/projections/nfl/{season}/{week}` on the same host answers the same
+    # shape (9,420 rows for 2021 week 16) and has no wrapper here yet.
+    #
+    # @param season [Integer, String] Season year, e.g. 2021
+    # @param week [Integer, String] Week number — required, see above
+    # @param season_type [String] "regular" (default), "pre", or "post"
+    # @param sport [String] Sport code (default: "nfl")
+    # @return [HTTParty::Response] Array of stat lines, each with `team`,
+    #   `opponent`, `game_id`, `date`, `week`, `season` and a nested `player`
+    def stats_with_context(season, week, season_type: "regular", sport: "nfl")
+      segments = [sport, season, week].map { |segment| ERB::Util.url_encode(segment.to_s) }
+      query = ERB::Util.url_encode(season_type.to_s)
+
+      make_request("/stats/#{segments.join("/")}?season_type=#{query}", host: WEB_HOST)
+    end
+
     # Get a season's game schedule.
     #
     # Undocumented, and served from the host root rather than /v1 — hence the
@@ -269,6 +351,26 @@ module SleeperApi
     # `post` (weeks 1-4) restart week numbering, so games from different season
     # types must never be pooled.
     #
+    # **`status` is `pre_game`, `in_game`, `complete` or `canceled`**, observed
+    # across the 2025 and 2026 regular seasons. `in_game` was read off a live
+    # game on 2026-09-10; the other three come from the published schedule. It
+    # is the only per-game signal of whether a game has been played — there is
+    # no kickoff time anywhere in this payload, only `date`, so a caller can
+    # know that a game is under way but never how far into it.
+    #
+    # **A week is not one event, and a caller reasoning from `date` alone will
+    # get that wrong.** Week 1 of 2026 held all three live states at the same
+    # moment: one `complete`, one `in_game`, fourteen `pre_game`.
+    #
+    # Treat the four as an open vocabulary. A postponement or a suspension
+    # would be a fifth value and none has been seen, so match with a fallback
+    # rather than a whitelist.
+    #
+    # **A team can carry two games in one week.** 2026 lists a canceled DAL/SEA
+    # in week 6 that was superseded rather than called off, and both teams play
+    # someone else that week. Order by status before picking one, or you will
+    # hand a team a bye it does not have.
+    #
     # A season Sleeper has not scheduled yet answers 200 with an empty array
     # rather than 404, so an empty result is a legitimate answer and not an
     # error.
@@ -336,29 +438,45 @@ module SleeperApi
 
     # Make an HTTP request with retry logic and logging.
     #
+    # ⚠️ **`host:` cannot be done by passing an absolute URL instead.** HTTParty
+    # 0.24 raises `UnsafeURIError` for any URL whose host differs from the
+    # configured `base_uri` — "this request could send credentials to an
+    # unintended server" — so a second host has to arrive as its own
+    # `base_uri`, which is a per-request option it supports.
+    #
+    # **The error and the log name the host whenever it is not the default.**
+    # `/stats/nfl/2021/16` is a real path on both hosts and they return
+    # different things, so a message quoting the path alone cannot say which
+    # one failed. Paths on the default host quote exactly as they always have.
+    #
     # @param path [String] API endpoint path
+    # @param host [String, nil] a different host, e.g. WEB_HOST
     # @return [HTTParty::Response]
     # @raise [SleeperApi::Error] On HTTP errors or timeouts
-    def make_request(path)
-      @config.logger&.info("Making request to #{self.class.base_uri}#{path}")
+    def make_request(path, host: nil)
+      named = host ? "#{host}#{path}" : path
+      options = { timeout: @config.timeout }
+      options[:base_uri] = host if host
+
+      @config.logger&.info("Making request to #{host || self.class.base_uri}#{path}")
       retries = 0
       begin
-        response = self.class.get(path, timeout: @config.timeout)
+        response = self.class.get(path, **options)
         if response.success?
-          @config.logger&.info("Successful response for #{path}")
+          @config.logger&.info("Successful response for #{named}")
           response
         else
-          @config.logger&.error("Failed to fetch #{path}: #{response.code}")
-          raise SleeperApi::Error, "Failed to fetch #{path}: #{response.code}"
+          @config.logger&.error("Failed to fetch #{named}: #{response.code}")
+          raise SleeperApi::Error, "Failed to fetch #{named}: #{response.code}"
         end
       rescue Net::OpenTimeout, Net::ReadTimeout => e
         retries += 1
         if retries <= @config.retries
-          @config.logger&.warn("Retrying #{path} (attempt #{retries}/#{@config.retries}) due to #{e}")
+          @config.logger&.warn("Retrying #{named} (attempt #{retries}/#{@config.retries}) due to #{e}")
           sleep(1)
           retry
         else
-          @config.logger&.error("Request timed out for #{path} after #{retries} retries")
+          @config.logger&.error("Request timed out for #{named} after #{retries} retries")
           raise SleeperApi::Error, "Request timed out after #{retries} retries"
         end
       end

data/lib/sleeper_api/json_parser.rb

@@ -0,0 +1,40 @@
+require "httparty"
+require "json"
+
+module SleeperApi
+  # HTTParty's JSON parser, minus the one argument that stops it working.
+  #
+  # HTTParty 0.24.2 parses with `JSON.parse(body, quirks_mode: true,
+  # allow_nan: true)`. **json 3.0 removed `quirks_mode`**, so every response
+  # this gem parses raises `ArgumentError: unknown keyword: quirks_mode` the
+  # moment a consumer resolves json 3 — which is total breakage, not a
+  # degradation, and it arrives through a transitive bump nobody asked for.
+  # httparty 0.24.2 is the newest release and has no fix.
+  #
+  # **Dropping the option rather than pinning json is what keeps this the
+  # gem's problem instead of its consumers'.** A `json < 3` constraint in the
+  # gemspec would fix the same crash by forbidding every app that uses this
+  # gem from upgrading json at all, for a flag none of them asked for.
+  #
+  # `quirks_mode: true` allowed a bare scalar at the top level. That is not
+  # academic here — Sleeper answers an unknown username with a literal `null`.
+  # Both majors parse that correctly without the flag, checked on 2026-09-11:
+  # `JSON.parse("null")` is `nil` under json 2.21.2 and under 3.0.2. The flag
+  # has been doing nothing for this gem for some time.
+  #
+  # **@api private.** It is public only because `parser` has to name something
+  # a consumer's Ruby can resolve. Nothing here is a promise: it exists to be
+  # deleted the day httparty parses without the flag, and it is why 1.3.1 is a
+  # patch rather than a minor — a new constant that is not API does not earn
+  # one, and a fix for total breakage should reach a `~> 1.3.0` pin.
+  #
+  # A subclass rather than a `parser` lambda, because everything else in
+  # `HTTParty::Parser#parse` still applies — the blank-body guard, the format
+  # detection, the supported-format table. One method is wrong; one method is
+  # overridden.
+  class JsonParser < HTTParty::Parser
+    def json
+      JSON.parse(body, allow_nan: true)
+    end
+  end
+end

data/lib/sleeper_api/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module SleeperApi
-  VERSION = "1.3.0"
+  VERSION = "1.4.0"
 end

data/lib/sleeper_api.rb

@@ -1,5 +1,6 @@
 require_relative "sleeper_api/version"
 require_relative "sleeper_api/helpers"
+require_relative "sleeper_api/json_parser"
 require_relative "sleeper_api/client"
 require_relative "sleeper_api/league"
 require_relative "sleeper_api/user"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sleeper_api
 version: !ruby/object:Gem::Version
-  version: 1.3.0
+  version: 1.4.0
 platform: ruby
 authors:
 - Eruity1
@@ -148,6 +148,7 @@ files:
 - lib/sleeper_api/client.rb
 - lib/sleeper_api/draft.rb
 - lib/sleeper_api/helpers.rb
+- lib/sleeper_api/json_parser.rb
 - lib/sleeper_api/league.rb
 - lib/sleeper_api/user.rb
 - lib/sleeper_api/version.rb