Skip to content

update - #4

Merged
LidorHefets merged 7 commits into
LidorHefrom
main
Apr 23, 2026
Merged

update#4
LidorHefets merged 7 commits into
LidorHefrom
main

Conversation

@LidorHefets

Copy link
Copy Markdown
Collaborator

No description provided.

Yuval added 6 commits April 21, 2026 12:54
…Layout

Moves /address-search under the MapLayout route so the persistent
Google Map stays mounted across navigation instead of being torn down
and rebuilt. AddressSearchMain now drives the shared map via MapContext
(setConfig/setOverlays/panTo/layerMode) rather than embedding its own
<APIProvider>/<Map>.

Also:
- Switch MapLayout to the real Google Cloud mapId (enables Advanced
  Markers and styled map rendering)
- Set APIProvider language="iw" region="IL" so Places/Geocoding return
  Hebrew results and IL-biased suggestions
The home pin used a wrapper transform: translate(0, -50%) to fake the
stem tip sitting on the address. AdvancedMarker anchors the content
box, not the transformed visual, so the pin drifted away from the
true lat/lng at different zoom levels.

Remove the transform and rely on AdvancedMarker's default anchoring
(bottom-center of content on coord), which puts the stem tip on the
address at every zoom.

Also wire onClick on the home marker to navigate to /address-search
with the user's full home address payload (lat/lng + city/street/house),
mirroring the route the top-search autocomplete already uses. Applied
on MainScreen and NearbyReportsScreen.
…k failures

Map login failure by HTTP status:
- 401 -> "סיסמא או שם משתמש לא נכונים"
- 0/undefined (network) -> "לא ניתן להתחבר לשרת, נסו שוב מאוחר יותר"
- 5xx -> "שגיאת שרת, נסו שוב בעוד מספר רגעים"
- other -> fall back to the error message, or a generic login error

Replaces the catch-all that leaked raw backend messages (or bare
"שגיאה בהתחברות") for wrong-password attempts.
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@LidorHefets
LidorHefets merged commit 97fc9f7 into LidorHe Apr 23, 2026
9 checks passed
Ovalvoi pushed a commit that referenced this pull request May 18, 2026
- Add `permissions: contents: read` (+ `security-events: write` for CI)
  to all four workflow files so they run with least-privilege tokens
  instead of the default over-broad GITHUB_TOKEN permissions.
- Sanitize `context.Request.Path` before logging in
  ExceptionHandlingMiddleware to prevent log-forging via CR/LF injection.
- Dismiss false-positive CodeQL alerts: #13 (AuthController UserId log
  is not PII) and #10 (ImageUploadModal preview is a blob URL, not HTML).
- Dismiss secret-scanning alerts #4/#5/#6: Firebase API keys are
  intentionally public and restricted via Firebase Security Rules /
  Google Cloud Console; they are not server-side credentials.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants