| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: chandi <git@chandi.it>
|
|
|
|
|
|
|
|
|
|
|
| |
Since we are about to release it's time to finally fix our linting. This
patch basically runs eslint --fix and does some further manual fixes.
Also it sets up eslint to fail on every warning on order to make
warnings visable in the CI process.
There should no functional change be introduced.
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
|
|
|
|
| |
Signed-off-by: Carles Bruguera <carlesba@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
The current error handling seems to conflict with some sequelize
versions. So we add a second version of it in our excemptions.
I'm not happy about it, but when it helps to prevent further migration
breaking, it's worth it.
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
|
|
|
|
| |
Signed-off-by: Hugo Caloto <hcaloto@gmail.com>
|
|\
| |
| | |
GDPR compliant part 1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the current setup users could be tricked into deleting their data by
providing a malicious link like `[click me](/me/delete)`. This commit
prevents such an easy attack and need the user's deleteToken to get his
data deleted. In case someone requests his deletion by email you can
also ask him for this token.
We can add a GUI that shows it later on.
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
|
|/
|
|
| |
Signed-off-by: Pedro Ferreira <pedro.ferreira@cern.ch>
|
|
|
|
| |
Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
|
|
|
|
| |
* Fix field type to prevent data truncation of authorship
|
|
|
|
| |
Signed-off-by: Takeaki Matsumoto <takeaki.matsumoto@ntt.com>
|
|
|
|
| |
truncation of data.
|
|
|
|
| |
Detect is using SQLite to add index
|
|
|
|
| |
Move 'unique' constraint to another statement (SQLite don't support set unique when addColumn)
|
| |
|
|
|
|
|
|
| |
Up and Down method must return a Promise.
breaking changes: docker-hackmd cannot initialize, because db:migration will fail
|
|
|
|
| |
add ‘use strict’ in all backend file
|
|
|
|
|
| |
Introduce JavaScript Standard Style as project style rule,
and fixed all fail on backend code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to ensure data integrity
|
|
|