Shareable resources
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- typescript
Línea de trabajo
No se nombran archivos, pruebas ni puntos de entrada de código. Empieza revisando los flujos del encabezado de la secuencia propuesta y del panel de detalles del jardín; después, determina qué recursos y qué comportamiento de dependencias están dentro del alcance. Para darlo por terminado, es necesario acordar un diseño de compartición antes de poder definir la implementación.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
An ability for users to publicly share their:
- Gardens
- Sequences
- Regimens?
- ???
How it could work
In a sequence header or on a garden details panel, add a SHARE button. Clicking the button could open a popup with a toggle switch to turn on sharing. Once sharing is turned on, the popup shows two sharing options:
- Share via link - this provides a unique link to send to others (in a support email) or post somewhere, such as the forum. Maybe something in the format:
my.farm.bot/app/sequences/shared/83jv7d3kiy0
If another (logged in) user clicks this link, the app would open to the sequences page, with the shared sequence loaded in the editor. There could be some banner up in the sequence header indicating that the sequence is a shared sequence, and all editing would be disabled. There could be a button to SAVE A COPY which would save a copy of the shared sequence to the account for modification/use.
If a logged out user clicked the link, a lightweight version of the app could be loaded to display the sequence with no editing allowed, and no other controls/page elements/nav. Maybe just a button to LOGIN TO SAVE A COPY
- Embed - this would provide an iframe (or oEmbed?) embed code that could be pasted into documentation, blog posts, the forum, etc. The embed content would be a lightweight version of the app to display the shared resource, without editing/nav capabilities. Maybe add a button to
OPEN IN APP.
Dependencies
An obvious problem with saving a copy of someone else's sequence is that the sequence will likely have dependencies (tools, plants, groups, subsequences) that the new account doesn't have. While a saved sequence without dependencies might not be that useful, I think the amount of work and potential consequences of saving with dependencies is too much.
- Saving with dependencies could become a total mess - it could create a ton of subsequences or plants that the user didn't have visibility to prior to saving the top-level resource.
- Users sharing their sequences might not want subsequences and their whole garden to be revealed by sharing the top-level resource. I suppose there could be an extra control put in place on the resource author's end, but that sounds messy and could still expose users to unintended amounts of data leaking if they forgot sharing was on and later modified the sequence, or they didn't wholly understand what dependencies were at stake.
A middle-ground idea is to make a copy of the sequence without dependencies, but display the original author's dependency names to be used as a blueprint for the new user to "re-wire" the sequence with their own dependencies in order to fully save it. Something like:
What are other thoughts, concerns, potential gotchyas?
- Lenguaje dominante
- TypeScript
- Estrellas
- 978
- Forks
- 357
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin 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 FarmBot/Farmbot-Web-App
-
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
FarmBot/Farmbot-Web-App#2505 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
FarmBot/Farmbot-Web-App#2498 · 2 comentarios · 1 reacción ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
FarmBot/Farmbot-Web-App#2467 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 20/100
FarmBot/Farmbot-Web-App#2463 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
FarmBot/Farmbot-Web-App#2416 ·
Todos los issues de FarmBot/Farmbot-Web-App
Issues similares
-
grep and find tools search inside VCS directories (.git, .svn, .hg, .jj)Posiblemente ocupada @acmerfight la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
earendil-works/pi#12084 ·
Los mantenedores suelen responder en 1 día
-
comp/desktop P3 type/feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NousResearch/hermes-agent#154285 ·
Los mantenedores suelen responder en 1 día
-
agent-reported bug from-app needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightly-labs/openbot#8154 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
jdx/mise-action#730 ·
Los mantenedores suelen responder en 1 día
-
area:cards enhancement hand-tail ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
fil-donadoni/tolaria#9275 ·
Los mantenedores suelen responder en 1 día