Skip to main content

Release v1.12.0

· 3 min read
Eugenio
Staff Engineer

BoatyBall Release Notes

🚀 New Features:​

UI — Google Maps integration upgrade​

  • Integrated new React-based Google Maps library.
  • Improved clustering and rerendering performance.
  • Introduced two map types: road and hybrid.
  • Improved labeling for mooring balls and POIs.

Backend — Common tracking module​

  • Introduced shared tracking system for backend events.
  • Adaptive UI refresh rate based on mooring reservation activity.
  • Reduced network payload by sending only changed mooring ball states.
  • Improved mooring ball listing performance by ~2× during extended sessions.

New mooring ball type​

  • Added support for Unaffiliated mooring balls (outside BoatyBall system).

Backend — Anti fast-blocking protection​

  • Prevented rapid API-based blocking of mooring balls.
  • Improved reservation integrity and fairness.

Feature — Owner & Manager management improvements​

  • Owners can now manage managers across all locations regardless of root location restrictions.
  • Support for individual location assignment per manager.
  • Added bulk removal of all locations from a manager.

Feature — Reports & scheduling alignment​

  • Backend collection service rescheduled to 11:30 with 10-minute intervals for improved alignment with payment timing.

Feature — Optional geo data​

  • Boater requests no longer require geo information for balls and POIs.

Feature — User experience improvements (Boater)​

  • Added “Unpaid” prefix below mooring balls until payment is completed.
  • Added notification for reservation cancellation when unpaid reservation expires (after 4 minutes).

🐞 Bug Fixes​

Issue #50 — POI redirect infinite loading​

  • Fixed infinite loading when redirecting to non-existent POI.

Issue #51 — Non-existent mooring ball display​

  • Fixed infinite loading screen when accessing invalid ball IDs.

Issue #53 — Owner create mooring ball default location error​

  • Fixed issue where default location was missing on direct page load or refresh.

Issue #54 — Location tree UX issue​

  • Made root locations foldable in Admin panel to improve navigation in large datasets.

Issue #152 — Hidden mooring ball exposure​

  • Fixed security issue allowing hidden mooring balls to be accessed via direct API calls.

Issue #153 — Incomplete location tree in Admin​

  • Fixed issue where only first 4 levels of location hierarchy were displayed.

Issue #154 — NULL check-in/out time error​

  • Fixed NULL values during child location creation in Admin/Owner workflows.

Issue #56 — Hidden ball access in reservations​

  • Prevented hidden mooring balls from being shown in Reservations panel.

Issue #57 — Incorrect password session handling​

  • Fixed improper session handling after incorrect password entry.
  • Improved authentication failure behavior.

Issue #6 — Existing user invite bug​

  • Fixed issue allowing incorrect invitation flow for already active users.

✨ Other Improvements​

Owner/Manager backend enhancements​

  • Improved manager assignment logic across all locations.
  • Enabled granular and bulk manager location control.

Geo request optimization​

  • Made geo information optional in Boater API requests.

🏷️ Tags​

backend, frontend, maps, performance, reservations, security, admin, owner, boater, bugfix, feature, tracking, api

!release_date: 2024-09-01