Feature/matb/add searchexternalid appconfig#670
Conversation
…nalLocations handling with appConfig integration
…y and crossorigin attributes for improved security
📝 WalkthroughWalkthroughAdded support for configuring Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…` configuration via App Config in version 1.96.21
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
packages/map-template/CHANGELOG.md (1)
8-12: Consider using "Added" category and improving grammar.This change adds new configuration capability rather than fixing a bug. Also, "can be now also" reads awkwardly.
✏️ Suggested changelog entry
## [1.96.21] - 2026-03-31 -### Fixed +### Added -- `searchExternalLocations` can be now also set via App Config. +- `searchExternalLocations` can now also be set via App Config.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/map-template/CHANGELOG.md` around lines 8 - 12, Update the changelog entry for version 1.96.21 by moving the note from the "Fixed" section to an "Added" section and rewording the bullet to improve grammar; specifically reference `searchExternalLocations` and state that the ability to configure it via App Config was added (e.g., "Added ability to configure `searchExternalLocations` via App Config.").
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/map-template/src/components/MapTemplate/MapTemplate.jsx`:
- Around line 711-715: The effect that computes showExternalLocations only
treats the appConfig value as the string 'true', so native boolean true from
appConfig is ignored; update the logic in the useEffect that reads
externalLocationsConfig to handle both boolean and string forms (e.g., if
externalLocationsConfig is defined, set showExternalLocations to
(externalLocationsConfig === true || externalLocationsConfig === 'true'),
otherwise fall back to searchExternalLocations) and then call
setSearchExternalLocations(showExternalLocations); keep the useEffect
dependencies (searchExternalLocations, appConfig) and reference the existing
symbols useEffect, externalLocationsConfig, showExternalLocations,
setSearchExternalLocations, searchExternalLocations, and appConfig when making
the change.
---
Nitpick comments:
In `@packages/map-template/CHANGELOG.md`:
- Around line 8-12: Update the changelog entry for version 1.96.21 by moving the
note from the "Fixed" section to an "Added" section and rewording the bullet to
improve grammar; specifically reference `searchExternalLocations` and state that
the ability to configure it via App Config was added (e.g., "Added ability to
configure `searchExternalLocations` via App Config.").
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 5284a129-b7c6-4599-8126-bb5704fe90d8
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
packages/map-template/CHANGELOG.mdpackages/map-template/src/components/MapTemplate/MapTemplate.jsx
Summary by CodeRabbit