Skip to content

leaflet-maps-plugin.md

Latest commit

 

History

History
44 lines (37 loc) · 2.07 KB

leaflet-maps-plugin.md

File metadata and controls

44 lines (37 loc) · 2.07 KB
title Leaflet Maps Plugin Context
  • Last updated: 2026-04-07

Project Snapshot

  • Project type: WordPress Gutenberg block plugin built with React
  • Local repo: /Users/aarongilani/Dev_Arena/React/leaflet-maps-plugin
  • Remote: git@github.com:Vincent-Design-Inc/leaflet-maps-plugin.git
  • Current branch: main
  • Worktree state: clean
  • Task code prefix: LFMP
  • Status: Completed

Current Task

  • LFMP-01 Issue #10 bailout fix | Completed: 2026-03-23

Working Context

  • User-provided reference: https://github.com/Vincent-Design-Inc/leaflet-maps-plugin/issues/10
  • Current PM read: the issue is causing the plugin to bail out in some cases and should be treated as a contained bug-fix lane for tomorrow, not a broad plugin enhancement pass.
  • Local stack:
    • @wordpress/scripts
    • react-leaflet
    • leaflet
    • WordPress block plugin with src/ and compiled build/

Likely Technical Risk Area

  • The strongest local signal is in /Users/aarongilani/Dev_Arena/React/leaflet-maps-plugin/src/api.js and /Users/aarongilani/Dev_Arena/React/leaflet-maps-plugin/src/LeafletMap.js.
  • Specific guard-risk notes:
    • hasRequiredData() calls this.isValidCPT(slug) without awaiting it, so the guard is not behaving like a real validity check.
    • hasRequiredData() dereferences response[0].acf without first confirming response[0] exists, which can throw on empty result sets and cascade into an early bailout.
    • fetchLocations() in LeafletMap.js bails when hasRequiredData() returns falsey, so weak guard handling can surface as a full plugin stop rather than a degraded state.

Estimate Assumption

  • 4h assumes the task is:
    • reproduce or reason through the bailout condition
    • fix the guard / validation path
    • run build or tests for verification
    • capture any needed note on the issue
  • Add 2h if the issue turns out to involve broader FacetWP, ACF, or REST-shape compatibility handling beyond the local guard logic.

Resolution Note

  • Update on 2026-03-23: user reported that the bug is resolved and the functionality is now working as expected.