Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Expose URL property on VTODO entries

Abierto
  • ¿Algo no está bien?
#8,533 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
56/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
backend

Línea de trabajo

The issue asks for each card’s VTODO entry to expose a URL pointing to that card’s Deck view, but does not name the code that creates VTODO entries or its tests. Start by locating the VTODO generation path and how board and card URLs are formed. Done means exported entries contain the requested URL and relevant tests cover it.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

0. Needs triage feature: dav
How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

When displaying cards in another client, I want to be able to link the user to the view of the card in the Nextcloud Deck app.

Other clients can be:

  • Nextcloud Calendar app
  • Other third-party clients

Describe the solution you'd like

For a card, the VTODO entry should have the URL property set pointing to https://example.com/apps/deck/#/board/${board}/card/${card}.

Describe alternatives you've considered

Trying to detect that a VTODO comes from Nextcloud deck and hardcoding apps/deck/#/board/${board}/card/${card} as URL for them.

Additional context

There is a solution with @nextcloud/event-bus in https://github.com/nextcloud/deck/blob/d11c9fdc02913cd84f625ca6ba1229c2edb29f4c/src/init-calendar.js with the following limitations:

  • it only works from Nextcloud apps
  • it does not allow the user/application to copy the link or open it in a new tab
Lenguaje dominante
JavaScript
Estrellas
1.4k
Forks
358
Merge medio
2 d 3 h
PR fusionados (30 d)
89

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nextcloud/deck

Todos los issues de nextcloud/deck

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.