a-b-street / a-b-street/ltn

Report a problem tool

Open
#389 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
21
Forks
7
PR merge metrics
No merged PRs in 30d

Description

> UI-wise, it would make sense to put a link "report a bug (+ export a Geojson)" in the top-right bar, accessible at any time
>
> Hmm... maybe. In [another project](https://npw.scot), we chose to put a small button in the bottom-left of the map:
>
> ![Image](https://github.com/user-attachments/assets/59e479cf-8f90-4f54-beae-cdfffc32c278)
>
> Users can opt into including their full project there:
>
> ![Image](https://github.com/user-attachments/assets/32b22e78-6d90-4e2e-bc78-adf5a764c732)
>
> I might split this out into a separate issue to do similar here.

_Originally posted by @dabreegster in [#387](https://github.com/a-b-street/ltn/issues/387#issuecomment-2976153464)_

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue references a UI feature for reporting bugs with GeoJSON export, similar to another project. Look at the existing UI components in the frontend code, likely in a directory like `src/ui` or `web-ui`. Find where the top-right bar or map overlay buttons are defined. The feature involves adding a clickable element that triggers a modal or form, and exporting GeoJSON data. Check how map state or project data is currently accessed and serialized to GeoJSON. A good starting point is to examine the code for the map interface and any existing modal/dialog components.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.