Decidir o futuro do cliente web: reconexão, abas, token e hospedagem
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Read apps/app/src/client/web.js around lines 34–39, then compare the web client’s documented limitations in README.md and docs/app.md. Record a decision in app.md covering the web app’s role, phase, limits, and criteria; if it continues, address the listed reconnection, multiple-tab, token-history, and key-custody questions. The issue leaves those product and security decisions open.
Written by the indexing model from the issue text.
Description
Contexto
A web não roda o nó: depende do varanda-serve local, não reconecta sozinha, uma aba por vez, e o endereço com token pode ficar no histórico. Um cliente hospedado exigiria um nó remoto e custódia de chaves. O piloto é móvel; o futuro da web está sem decisão.
Escopo
- Decidir o papel da web (desenvolvimento, desktop, nenhum)
- Se continuar: reconexão automática, várias abas, token fora do histórico, onde ficam as chaves
Critérios de aceite
- Decisão registrada no app.md com fase, limites e critérios
Fontes
Fase: sem fase definida · Dificuldade: média
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Varanda-org/varanda
-
área:app área:produto sem-fase tipo:decisão
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Varanda-org/varanda#91 ·
-
área:identidade área:produto sem-fase tipo:verificação
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#93 ·
-
área:identidade área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#92 ·
-
área:moderação área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#90 ·
-
área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#89 ·
All issues in Varanda-org/varanda
Similar issues
-
bug needs triage P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pbakaus/impeccable#1143 ·
Maintainers usually reply within 1 day
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
next() is called twice when the request closes after busboy fails to startPossibly taken @NgoQuocViet2001 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[2.x] extension-manager: translation keys that changed meaning keep their old namesPossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day