Skip to content

Challenge validation #54

Description

@pbochis

When creating a challenge validate the fields:

  • non-empty name, description, instructions
  • duration validated according to challenge type
    • paralel: not lower than longest task
    • sequential: not lower than sum of all tasks' durations

Activity

  1. lorenzleutgeb commented on Aug 13, 2015

    @lorenzleutgeb
    Contributor

    @pbochis Why is this labeled perf?

  2. tudorgergely commented on Aug 14, 2015

    @tudorgergely

    How do we determine if a challenge is parallel or sequential? For now I see that all created challenges are sequential

  3. lorenzleutgeb commented on Aug 14, 2015

    @lorenzleutgeb
    Contributor

    @Tudy23 As for determining: Not so straightforward. This information is currently encoded in Challenge.Assignment.Endpoints.WebInterface. We should probably be more explicit about it and store sequential/parallel in a separate property. Creation: That's true. Creating parallel challenges needs to be done.

  4. tudorgergely commented on Aug 14, 2015

    @tudorgergely

    Then for now I will do the validation for duration as sequential. I will also create a issue regarding challenge type selection. I also think the type of a challenge should be stored separately, not determined based on the endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions