Skip to end of banner Go to start of banner

User

Skip to end of metadata

Created by Darya Tarasowa, last modified by Kurt Junghanns on Aug 09, 2016

Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Responsible: Kurt Junghanns

objectid = {
	type: 'string',
	maxLength: 24,
	minLength: 24
};

user =

property	type	required	format checking	state of implementation (master branch) in terms of attribute added and connected with the frontend
_id	integer, autoincrement	yes	isInteger	autoincrement - not implemented
email	string	yes	isEmail, unique	unique - not implemented isEmail - controlled by ajv
username	string	yes	unique	unique - not implemented
password	string (contains SHA512)	yes	alphanumerical	hash is generated on frontend
defaults	[ object ]	no	normally just an object with one key	not correctly implemented for now should decide on the preferences data model,
registered	date	yes	date	need to decide on the date format
surname	string	yes		implemented
forename	string	yes		implemented
gender	'male', 'female', null	no	null value should be possible	not implemented
locale	string	no	need to decide on the format	implemented
hometown	string	no		implemented
location	string	no		implemented
languages	array of languages	no	language (see below)	see language
picture	string	no		not implemented
interests	string	no		not implemented
description	string	no		not implemented
birthday	date	no	date	not implemented
infodeck	objectId	no	isInteger, deck exists with such id	not implemented

Not yet implemented: preferences =

property	type	required	format checking	state of implementation
_id	integer, autoincrement	yes	isInteger
language	language	yes	isValidLanguage
theme	objectId	yes	theme exists with the id

No labels