d120/pyfeedback

Jede Veranstaltung muss einen Ergebnissempfänger haben

Open

#96 opened on Mar 28, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (4 forks)auto 404
Good first issueeasy

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

Das wird derzeit nicht erzwungen. ist nötig damit der evasys export die veranstaltung akzeptiert

Erzwingen muss im Model der Veranstaltung erfolgen.

Gitlab 21

Contributor guide

Research direction
Add a model validation to enforce that every event has a result recipient before saving. Look at the Event model definition and add a constraint or custom validator.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65