jbr 5.0.0 → 6.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a01ddd16fc41518ff9cc7d18b61bdc2c0d9e419959c01fc7dd822473de08bade
-  data.tar.gz: 3d60fe2c06fd056d0e61d83bca1e40ff6f61954994a061e858a60422b6546e12
+  metadata.gz: cabf4447471fd3556e99cc05251c04a201f6329864d98d0650ba8506ff1dcc0a
+  data.tar.gz: 8149a10d060f9c265c82a482a53c3eb5646fcb744e41bd8ee136a4eb6b3b3cc5
 SHA512:
-  metadata.gz: 71b4e3faacce7acb0ea6d5a3eab5f1beea5f4534a416a16ed663d434299551b94375e3522f0152e6627a22340a7c098eaf464fdcec0012688fa07b0def98c9e8
-  data.tar.gz: 99828c97615dd6357dd58f167ec05338b6595cbcf5206cbad1088f9e3d3a95665f08698add77b3aeb854d4e10c9a664f8b77467ac064c680ecdd409bc763e96f
+  metadata.gz: 770c8fe0d7556995d4484c51953aeb009f06046910d07a7153f1d40a302be2f65a510becbe5bf523375e927367bfe37acde4bc71382e4fe8807f14e0b9cb9c74
+  data.tar.gz: 4e479fa10591e9bee8d2cc1c30a79355329d1233410dde79f48a0d094944366ff61bcc6b4e9d582eed4f1bdab27d8b4a2650a8d3f04ac2f2611ad42eca515b56

data/CHANGELOG.md

@@ -1,5 +1,23 @@
 ## [Unreleased]
 
+## [6.0.0] - 2026-09-16
+
+- [Breaking change] The vocabulary is `company` 3.0: `assigned_to` is `of`, so
+  `account.visits.of(technician)` is what `account.visits.assigned_to(technician)` was. Jobber
+  still narrows it in the one filter, and it still needs no Users scope. The pin is `~> 3.0`.
+
+- [Note] `account.windows` -- the free time of a business -- raises `NotImplementedError` here,
+  and will until Jobber exposes the hours a business keeps. It does not today: the schema was
+  enumerated looking, and there is no `BusinessHours`, `WorkingHours`, `Shift` or `Weekday` type
+  of any kind, while `OnlineBookingConfiguration` is four fields and none of them is an hour.
+
+- [Note] Every setting around those hours is there, on `requestSettings`:
+  `intervalDurationMinutes` is the grain, `earliestAvailabilityMinutes` the notice,
+  `bufferDurationMinutes` the padding either side of a job, `efficientSchedulingType` and
+  `maxDriveTimeMinutes` whether travel counts. A caller can work free time out from those and
+  the visits. Read them off the form that books, not the one marked default, whose
+  `bookingType` may be `NONE`.
+
 ## [5.0.0] - 2026-09-15
 
 - [Feature] A scope the app was never granted no longer raises. Jobber answers `An object of

data/README.md

@@ -115,7 +115,7 @@ failing. What each reader here needs:
 | --- | --- |
 | `account.jobs`, `job.lines` | Jobs |
 | `job.location`, `location.customer`, `visit.job` | Jobs and Clients |
-| `account.visits`, `assigned_to` | Scheduled Items |
+| `account.visits`, `of` | Scheduled Items |
 | `account.technicians`, `visit.technicians`, `includes(:technicians)` | Users |
 | `account.quotes` | Quotes |
 | `account.invoices` | Invoices |
@@ -125,7 +125,7 @@ Jobber files a visit under **Scheduled Items**, which is one object covering vis
 assessments, tasks and calendar events -- so there is no scope to add for the kinds of booked
 time this gem does not read yet.
 
-`assigned_to` is the one worth knowing: narrowing to a technician needs no Users, because
+`of` is the one worth knowing: narrowing to a technician needs no Users, because
 Jobber does the narrowing and no user is ever selected. Reading *who* is on a visit is what
 needs it.
 
@@ -325,17 +325,40 @@ One technician's week is the visits in it narrowed to them:
 
 ```ruby
 monday = Date.today.beginning_of_week.in_time_zone
-account.visits.between(monday, monday + 1.week).assigned_to(technician).each do |visit|
+account.visits.between(monday, monday + 1.week).of(technician).each do |visit|
   visit.starts_at, visit.ends_at, visit.job.id
 end
 ```
 
-Jobber narrows a list of visits by who is on it, so `assigned_to` puts the technician into the
+Jobber narrows a list of visits by who is on it, so `of` puts the technician into the
 same filter as the window: nobody else's visits are answered, paged or paid for, and the crew
 is not read at all unless `includes(:technicians)` asks. The two narrowings land in the one
 filter, so a caller may ask for the week and the technician in either order.
 
-`assigned_to` therefore needs no Users scope. Reading *who* is on a visit does.
+`of` therefore needs no Users scope. Reading *who* is on a visit does.
+
+## What Jobber cannot say
+
+`account.windows` -- the free time of a business, which the vocabulary names -- raises
+`NotImplementedError` here, and will go on doing so until Jobber exposes the hours a business
+keeps.
+
+It does not today. The whole schema was enumerated looking for it: there is no `BusinessHours`,
+`WorkingHours`, `OperatingHours`, `Shift`, `Weekday` or `DayOfWeek` type of any kind, and
+`OnlineBookingConfiguration` is four fields -- whether bookings are on, the URL, the embed
+script, the id. Jobber's own booking page must know the hours; the API does not say them.
+
+What it does say is every setting around them, on `requestSettings`:
+`intervalDurationMinutes` is the grain an offer is cut to, `earliestAvailabilityMinutes` the
+notice the business needs, `bufferDurationMinutes` the padding left either side of a job, and
+`efficientSchedulingType` with `maxDriveTimeMinutes` whether travel is counted as well. Read
+those beside the visits and a caller can work free time out for itself -- which is what the
+missing reader would have done. Take the settings from the form that books, not the one marked
+default: the default form may be a request form, whose `bookingType` is `NONE`.
+
+Raising is deliberate rather than answering with none. An empty week and a fully booked one are
+the same shape, so a caller reading none as none would quietly stop offering the business
+altogether, with nothing in a log and no page looking wrong.
 
 A visit is still not all Jobber schedules. A task, an event and the two kinds of reminder sit
 on the same calendar and are read past unread, because Jobber's filter takes one kind and not

data/lib/jbr/collections/visits.rb

@@ -24,7 +24,7 @@ module Jbr
     # @param technician [Company::Technician] whoever the work is booked for.
     # @return [Visits] the same list, narrowed to what they are booked for.
     # @note Needs no Users scope: Jobber narrows, and no user is selected to do it.
-    def assigned_to(technician) = narrowed(assignedTo: [ technician.id ])
+    def of(technician) = narrowed(assignedTo: [ technician.id ])
 
     # @return [Visits] the same list, narrowed to the stops of jobs, by Jobber rather than here.
     def for_jobs = narrowed(scheduleItemType: 'VISIT')

data/lib/jbr/version.rb

@@ -1,5 +1,5 @@
 # A Ruby client for the Jobber API.
 module Jbr
   # The version of this gem.
-  VERSION = '5.0.0'
+  VERSION = '6.0.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jbr
 version: !ruby/object:Gem::Version
-  version: 5.0.0
+  version: 6.0.0
 platform: ruby
 authors:
 - Claudio Baccigalupo
@@ -29,14 +29,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.1'
+        version: '3.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.1'
+        version: '3.0'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement