Naming LTI links

Abierto
#2,578 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
perl
Área
backend

Línea de trabajo

The issue names no files or tests. Start by finding where the LTI content item selection code sets the title and description of generated links in the repository. The open question is whether the fix should be a configurable prefix or a description change, and the thread does not settle it. A newcomer should first ask a maintainer which option they want. Done means the chosen approach is implemented and a test covers the generated title or description.

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

Descripción

In a WeBWorK course, you might have an exercise set titled 'Adding Rational Expressions'. You are in WeBWorK, so of course this is a WeBWorK assignment covering that topic.

In the LMS, when you use content item selection to automatically create LTI links to sets in your WW course, the LTI link will have title 'Adding Rational Expressions'. At least in D2L, there is nothing that automatically conveys how this is a link to a WeBWorK set. Based on its title, you might think clicking it will take you to a lesson on that subject. Of course, you can edit the title and description, but it would be nice if the LTI link was initially generated in a way that, for example, makes the title be 'WeBWorK assignment: Adding Rational Expressions'. And/or adds something to the description mentioning WeBWorK.

I could just force it to prepend 'WeBWorK assigment: ' but I wanted to ask if we thing there's a better, configurable way to accomplish the goal.

Lenguaje dominante
Perl
Estrellas
164
Forks
167
Merge medio
6 d 7 h
PR fusionados (30 d)
27

Preparar el entorno

  • 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 openwebwork/webwork2

Todos los issues de openwebwork/webwork2

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.