Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Required Achievement don't yet have scope check #37

Open
GoesOnTangents opened this issue Jun 20, 2018 · 1 comment
Open

Required Achievement don't yet have scope check #37

GoesOnTangents opened this issue Jun 20, 2018 · 1 comment
Labels

Comments

@GoesOnTangents
Copy link
Contributor

Currently

Scope is defined on .scope and regards events from <achievement.requirements.event, but not <achievement.requirements.achievements

Issue

  • It is unclear for a configurator where the service will check for correct scopes
    1. scope should regard every requirement (both events AND, newly, achievements)
    1. achievement scopes could be handled in requirements.achievements..scope
@frederike-ramin
Copy link
Contributor

We decided for ii because sometimes you don't want to have the same scope as for the new achievement.

@cmfcmf cmfcmf added the scope label Aug 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants