merge Main into DevelopNXT - #588
Merged
Merged
Conversation
# [1.45.0](WatWowMap/ReactMap@v1.44.3...v1.45.0) (2026-07-05) ### Bug Fixes * invasion reward icon size logic ([4806148](WatWowMap@4806148)) ### Features * client option to use invasion rewards as marker ([7b24b32](WatWowMap@7b24b32)) * questLayerMode defaulting to non_ar ([925c8ed](WatWowMap@925c8ed))
…wMap#1225) (WatWowMap#1226) * fix(scanArea): prevent crash when area feature has no name/key Guard the scan area search filter against features missing a properties.key (which happens when a scan area polygon has no name set), instead of throwing TypeError: Cannot read properties of undefined (reading 'toLowerCase'). Also fixes a longstanding typo (geoJsonFilName / geoJsonFilname -> geoJsonFileName) in the multi-domain example config and docs. * fix: copilot comments --------- Co-authored-by: turtlesocks-bot <turtlesocks-bot@users.noreply.github.com> Co-authored-by: PJ0tter <pjorritsma@users.noreply.github.com>
## [1.45.1](WatWowMap/ReactMap@v1.45.0...v1.45.1) (2026-07-05) ### Bug Fixes * **scanArea:** prevent crash when area feature has no name/key ([WatWowMap#1225](WatWowMap#1225)) ([WatWowMap#1226](WatWowMap#1226)) ([2df8c9e](WatWowMap@2df8c9e))
# [1.46.0](WatWowMap/ReactMap@v1.45.1...v1.46.0) (2026-07-11) ### Features * mega branch resource with fallback ([8756f38](WatWowMap@8756f38))
# [1.47.0](WatWowMap/ReactMap@v1.46.0...v1.47.0) (2026-07-21) ### Features * support PokéCoin quest filtering ([1d5d142](WatWowMap@1d5d142))
## [1.47.1](WatWowMap/ReactMap@v1.47.0...v1.47.1) (2026-07-21) ### Bug Fixes * bounded early-exit ([b382a2c](WatWowMap@b382a2c)) * quest target filtering logic ([96e59d6](WatWowMap@96e59d6))
## [1.47.2](WatWowMap/ReactMap@v1.47.1...v1.47.2) (2026-07-21) ### Bug Fixes * pokecoin amount methinks ([9f41f72](WatWowMap@9f41f72))
# [1.48.0](WatWowMap/ReactMap@v1.47.2...v1.48.0) (2026-07-21) ### Features * mega branch resource icon support ([b35507f](WatWowMap@b35507f))
Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.2 to 3.1.4. - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.2...v3.1.4) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
## [1.48.1](WatWowMap/ReactMap@v1.48.0...v1.48.1) (2026-07-22) ### Bug Fixes * availability bootstrap ([520c1f1](WatWowMap@520c1f1)) * no more reward types ffs ([b4e2f71](WatWowMap@b4e2f71))
…atWowMap#1231) * fix(webhooks): stop GPS ticks overwriting the saved Poracle location The notification panel listened for Leaflet `locationfound` events and persisted every one of them via the `setLocation` mutation. Because `leaflet.locatecontrol` runs geolocation in watch mode, an active locate control keeps emitting position fixes for as long as it is running, so simply opening the panel was enough to silently rewrite a location the user had deliberately set elsewhere. Users who track by coordinates + distance are hit hardest: Poracle stores one lat/lng per human, so a single background tick moves every distance-based tracking they have. Reported by a user who set alerts for a park, then had them follow him home the next time he edited a tracking. Gate the handler behind a ref that only the "My Location" button arms, and consume it on the first event so a continuing watch cannot write again. `_onClick` toggles the control, so arm from `_active` after the call -- clicking it while active stops locating and no event is coming. Also fix two adjacent issues found while verifying: - The coordinate comparisons required *both* lat and lng to differ, so moving a pin along a single axis never saved. - `human` is empty until the query resolves, so the init effect seeded the store with `[undefined, undefined]`, and its `every(x => x === 0)` guard then never re-fired once real coordinates arrived. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(webhooks): clear pending locate when a location is saved A GPS fix can take many seconds on mobile. If the user clicked My Location and then picked a different location via search or Choose on Map while waiting, the ref stayed armed and the late fix overwrote the newer explicit pick -- reintroducing the silent overwrite through a race. Clear the pending request whenever a location is actually persisted, so the most recent deliberate choice wins. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(webhooks): avoid duplicate setLocation POST from sync effect Search and My Location call handleLocationChange directly, which writes the store and POSTs. That store write re-fires the webhookLocation sync effect (kept for the drag picker, whose only signal is the store), which then POSTs the same coordinates a second time. Switching the comparison to || widened this to single-axis moves as well. Track the coordinates currently being persisted in a ref and short-circuit the effect when it would only duplicate that in-flight save, clearing the ref once the mutation settles (guarded so a newer save isn't wiped by an older one). The drag picker still routes through the effect and saves exactly once. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This reverts commit 5772469.
## [1.48.2](WatWowMap/ReactMap@v1.48.1...v1.48.2) (2026-07-24) ### Bug Fixes * **webhooks:** stop GPS ticks overwriting the saved Poracle location ([WatWowMap#1231](WatWowMap#1231)) ([0f27862](WatWowMap@0f27862))
This reverts commit f179b43.
## [1.48.3](WatWowMap/ReactMap@v1.48.2...v1.48.3) (2026-07-24) ### Bug Fixes * escape username ([f817d75](WatWowMap@f817d75))
## [1.48.4](WatWowMap/ReactMap@v1.48.3...v1.48.4) (2026-07-25) ### Bug Fixes * more robust masterfile ([e68a4f9](WatWowMap@e68a4f9))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.