Consignment market: list items to sell while offline (port the fork's feature; server is ours)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- full-stack
Línea de trabajo
Start by judging the seven forkmap "Consignment market" cards, which exist only in the maintainer's ledger, and read stall_network.go to see how town selling works today. The server work (listing store, expiry, settlement, return to warehouse or bag, commission) is design-heavy and needs the owner's fee and limit approval first. Done means the SRO_CONSIGNMENT flag and an Experimental client row both pass tests when on and off.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Players asked for it on Discord (2026-11-15), and the owner wants it.
What exists today
- The v1.150 client has no consignment: no window, no text (0 matches for "consign" in its UI strings). The stall network (
stall_network.go) is the only way to sell from towns. - A downstream fork already ships a consignment market in its browser client. In the forkmap ledger (laptop,
handover/forkmap/work) it is the registered feature Consignment market. Seven items mention it, all unjudged: H-ec5fdff3, H-5dce0496, H-eb911134, C-75948b85, C-51d6ce00, C-6199d551, and C-d44d967b (SUPPORT, option-row plumbing). - What their client shows: a CONSIGNMENT window on its own hotkey, item search, "My listings", listing from the inventory by drag, and sale notices: sold, sold to a named buyer, did not sell and returned to the warehouse or the bag, "warehouse is full, take it back from My listings", "Consignment is closed right now".
What we can and cannot take
- Their client half can be read from the served bundle through forkmap. Their server cannot: they do not share code. The server half (listing store, expiry, sale settlement, return to warehouse, the commission) is ours to write.
- Their strings are their own Turkish/English text, not a native catalogue.
Done when
- The forkmap "Consignment market" cards are judged (what each one does; which we take).
- Server: listings persist across restarts, expire and return items (warehouse, else the bag), pay the seller, take a fee, and hold up against duplication and abuse (an item is in exactly one place at every step).
- Client: the window, search, My listings, the notices.
- Ships behind
SRO_CONSIGNMENT(port-only, not native; off is native) plus an Experimental row for the client entry, both tested on and off. - The owner approves the fee and the listing limits before it turns on.
- Lenguaje dominante
- Go
- Estrellas
- 97
- Forks
- 61
- Merge medio
- 4 h 14 min
- PR fusionados (30 d)
- 913
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de opensro-dev/opensro
-
area: client enhancement priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#3681 ·
Los mantenedores suelen responder en 1 día
-
area: client bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
opensro-dev/opensro#3228 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Format one minified client file with dprint (ongoing: one file per PR)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea: client enhancement good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
opensro-dev/opensro#1 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: server bug priority: medium
Dificultad 3/5 Medio día Aptitud para principiantes 55/100
opensro-dev/opensro#3687 ·
Los mantenedores suelen responder en 1 día
-
area: ops bug priority: high
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
opensro-dev/opensro#3685 ·
Los mantenedores suelen responder en 1 día
Todos los issues de opensro-dev/opensro
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
unbound-force/gaze#353 ·
Los mantenedores suelen responder en 1 día
-
bug cross-seed ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
OneBusAway/maglev#2102 ·
Los mantenedores suelen responder en 2 días
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Los mantenedores suelen responder en 1 día