Implement self-described user concept and api#12
Open
mo-g wants to merge 6 commits into
Open
Conversation
mo-g
force-pushed
the
userconcept
branch
2 times, most recently
from
4f8af65 to
302de9d
Compare
mo-g
force-pushed
the
userconcept
branch
2 times, most recently
from
99c96b3 to
527a443
Compare
Contributor
Author
|
Something I need to spec out in more detail is define what the scope is of each section. Some parts of a User object are useful only to the Agent, some are needed by the badge protocol. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Going to build a user concept and implement an impermanent API to register, modify and delete them. May leave the linking of users to badges to a later merge, may not. We'll see! Permanence will definitely come later, as currently there is no permanence in Spindoctor. We need a system of recording badges, users, locations, targets - but there's no point worrying about any of these till the basic functionality is implemented.
API will launch with a template/fallback user which will be used as a default when manual users have not been populated. This will also serve as a template for the API to self-describe.