UserOption are not meant to be use in labelstower demo app.
It is used in other project such as CodingPoolBack to join ELEMENT table
to User table (ELEMENT.user_id->User.id).

The demo does have user table and ELEMENT are not link to user.
This option is used in other project such as CodingPoolBack.

Set UserOption variable to true to get username related to element
by ELEMENT.user_id.

The two file are a set python variables(key/value).
Keys are identical in each file in order to create a kind of interface
that can either use variables from one file or the other.
values are queries and indexes.
queries is a list of two sql statement executed to select tutorials with
mandatories and/or forbiden labels.
Inside sqlStmtUser.py ELEMENT table is join to User table but not in
sqlStmt.py. With sqlStmtUser.py result of select have an extra column :
username related to element (e.g. because they are the creator of this
element).

Doctest must return an error code in case of failure

See merge request !68

Customisable labelstower

See merge request !67

dict keys are changed because of the customisable new behavior of
labelstower blueprint.

select all attributs from element talble in order retrieve all attributs that
developper declared in app/models.py.

I refactor the first sql statement to let the developper define is element structure.
The only mandatory attribut for element table will be id. The rest is up to the developper.

We don't know how the label and element tables will b.
That's is the reason why we reused element and label structure
define by the developper of labelstower framework.

incremente version

See merge request !65

Reproduction de la structure mise au point dans CodeGuards

See merge request !64

Reproduction de la structure de CodeGuards, à LT_CFG prêt, et il reste du travail sur les tests unitaires de getter.py

Master

See merge request !63

Packager labelstower bis

See merge request !62

Packager labelstower

See merge request !61