[User Story] Show map using location data
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 停滞
- 技術スタック
- javascript
調査の方向性
まず、issue #181 で参照されている駐車報告フローと GPS 認証の作業箇所を見つけます。チェック済みの受け入れ基準がすでに実装されているか確認します。完了とは、ユーザーの位置を地図上に表示し、「Atualizar localização」で再試行できるようにすることです。deskcheck に記載されているユニットテストのカバレッジも確認します。
索引モデルが issue の本文から書いたものです。
説明
User story
As a user who is creating a parking report
I want to view a map with the location of the car
So that I can confirm that I am informing the correct place
Business context
In order to submit a report with enough information for authorities to eventually take action, the localization of the user is necessary. Without this information, it would be difficult to identify where the car is parked, even with car plate information. After obtaining user authorization to get their location (#181), we need to show the result to the user as a map.
Describe alternatives you've considered
It would be also possible for the user to type their address, instead of using GPS.
In scope
- Give user the chance to try to obtain the address again, by clicking on "Atualizar localização".
Out of scope
Show map with address to the user on the same screen.
Ask for user permission to use GPS (#181 ).
Offering a field for the user to type their address, in case the GPS was incorrect, not available, or the user did not authorize using GPS (#208).
Acceptance Criteria
- 1. Happy path (user sees the correct location on map)
Given the user has chosen an image to proceed with the parking report
When the user clicks to accept informing their position by GPS
Then the page shows "obtendo localização"
Then the page shows the map with the user location marked. - 2. Alternative path (give user the chance to try to click and see address again)
Given the user has seen the map with the address marked
When the address marked is wrong
Then the user can click on "atualizar localização" to try again
Checklist do kickoff
- A análise da história está concluída?
- QA (ou pessoa que assumiu o papel de QA) revisou a análise?
- A história está completa com todos os detalhes e as informações relevantes?
(Ex.: Contexto, Escopo, Fora de Escopo, Critérios de aceite, etc); - O valor de negócio da história está bem entendido? (se aplicável)
- Esta história não tem dependência de outras histórias futuras?
- Não existem dívidas técnicas (débitos técnicos) relacionadas a história;
- Há protótipos de telas para essa história (se aplicável)
- Há detalhes na história de mensagens de erro e outros feedbacks para o usuário (se aplicável)
- Há mensagens de ajuda ou outros textos definidos na história (se aplicável)
- A história está em um tamanho adequado
- Existe feature toggle para a feature (se aplicável)
Checklist do deskcheck
- Há testes unitários que validem a implementação? (se aplicável)
- As alterações de código passaram em todas as pipelines
- A história foi executada manualmente
- A história não trouxe regressões ou impacto negativo a outras implementações
- Todos os critérios de aceite foram cobertos
- A história não precisa de feedback ou correção
- Foi testada uma jornada completa do usuário através da história (se aplicável)
- 主要言語
- JavaScript
- スター
- 3
- フォーク
- 2
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
multei/web のほかの issue
-
dependencies todo :spiral_notepad:
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
メンテナーはふだん 1 日以内に返信
-
dependencies todo :spiral_notepad:
難易度 4/5 3〜5日 初心者へのやさしさ 55/100
メンテナーはふだん 1 日以内に返信
-
dependencies todo :spiral_notepad:
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
メンテナーはふだん 1 日以内に返信
-
dependencies todo :spiral_notepad:
難易度 4/5 3〜5日 初心者へのやさしさ 52/100
メンテナーはふだん 1 日以内に返信
-
dependencies todo :spiral_notepad:
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
似ている issue
-
Complexity: Small P-Feature: Projects page ready for merge team role: back end/devOps role: front end size: 0.25pt
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 67/100
bellingcat/toolkit#905 ·
-
self-care self-care:docs-build-time-investigator
難易度 2/5 半日 初心者へのやさしさ 76/100
githubnext/gh-aw-cao#14191 ·
メンテナーはふだん 1 日以内に返信
-
effort:low impact:medium RAG status: auto-triaged
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
mastra-ai/mastra#25229 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
sugarlabs/musicblocks#8984 ·
メンテナーはふだん 1 日以内に返信