Missing relationships

Abierto
#170 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
ruby

Línea de trabajo

Start by reading the models and relationship definitions for cards, printings, restrictions, cycles, sets, pools, subtypes, formats, and snapshots. The issue lists candidate missing relationships but leaves it undecided which should be implemented and whether the restriction-to-format relationship is one-to-one or one-to-many. Done means agreeing on the intended relationships and adding the selected definitions with coverage for fetching them.

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

Descripción

enhancement

I think we would benefit from having:

  • a relationship from cards/printings to their card type (so it can be fetched with an include)
  • a relationship from card/printings to restrictions (ditto)

Also some existing relationships are missing their inverses:

  • card does not have a hasMany relationship back to card_cycle
  • card_cycle, card_set, and card do not have a relationship back to card_pool
  • card does not have a relationship back to card_set
  • printing does not have a relationship back to card_subtype
  • restriction does not have a relationship back to format (I'm not sure if this would be a hasMany or hasOne relationship)
  • card_type does not have a relationship back to printing
  • card and restriction do not have a relationship back to snapshot

I don't know if all/any of these need implementing, but I think this is all of the missing ones.

Lenguaje dominante
Ruby
Estrellas
10
Forks
9
Merge medio
2 h 59 min
PR fusionados (30 d)
2

Preparar el entorno

Abrir en Codespaces

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

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 Null-Signal-Games/netrunnerdb-api-server

Todos los issues de Null-Signal-Games/netrunnerdb-api-server

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.