hedgedoc/lib/migrations, branch cindy Hedgedoc with support for CindyScript Add missing catch 2020-12-02T18:39:06+00:00 Tilman Vatteroth 2020-12-02T18:39:06+00:00 0318ce3e8347342309f6f75f72b6ed5a83b03e52 Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de> 
Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
Catch more errors 2020-12-02T16:22:27+00:00 Tilman Vatteroth 2020-12-02T16:22:27+00:00 120225947f6c22c8e7f8b9c2b72f496784162647 Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de> 
Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
[Migrations] Replace similar code 2020-11-30T16:39:50+00:00 Tilman Vatteroth 2020-11-30T16:39:50+00:00 4ae80a3ed08aac4dddc2bddb80b5da5d7e20df86 Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de> 
Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
[Migrations] Add variant of error message to catch block 2020-11-30T16:31:55+00:00 Tilman Vatteroth 2020-11-30T16:31:55+00:00 a157599884c98667ca8dc608e6de4d70d0a1812d Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de> 
Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
Add fix for missing deletion of notes on user-deletion request 2020-03-21T15:14:43+00:00 Sheogorath 2020-03-21T15:07:14+00:00 a9d98d4b529e6dd4a4f978dd8facd4bf5a20861e Depending on how the system was setup, this bug lead to keep user's data around even after a successful deletion of user'S account. This patch will make sure the missing database constraints are implemented and missed out deletions are executed. This bug was introduced to insufficent testing after implementing the feature initially. It was well tested, using the app process itself, but the migrations where missed out. I'm currently not sure, if there was also a change in how sequelize handles cassaded deletion, since I'm unter the impression that before switching to sequelize 5, this feature has worked. But I haven't verified this. No matter what, the cleanup process is rather straight forward and will be invoked on migration, but can also be done manually using the new `bin/cleanup` script. This change will result in a release 1.6.1. Signed-off-by: Sheogorath <sheogorath@shivering-isles.com> 
Depending on how the system was setup, this bug lead to keep user's data
around even after a successful deletion of user'S account. This patch
will make sure the missing database constraints are implemented and
missed out deletions are executed.

This bug was introduced to insufficent testing after implementing the
feature initially. It was well tested, using the app process itself, but
the migrations where missed out. I'm currently not sure, if there was
also a change in how sequelize handles cassaded deletion, since I'm
unter the impression that before switching to sequelize 5, this feature
has worked. But I haven't verified this.

No matter what, the cleanup process is rather straight forward and will
be invoked on migration, but can also be done manually using the new
`bin/cleanup` script.

This change will result in a release 1.6.1.

Signed-off-by: Sheogorath <sheogorath@shivering-isles.com>
fix: migration should return promise 2019-08-12T12:13:34+00:00 chandi 2019-08-12T12:08:31+00:00 6280e92d1042967e16e68a50b6364de566e266ef Signed-off-by: chandi <git@chandi.it> 
Signed-off-by: chandi <git@chandi.it>
Fix eslint warnings 2019-05-30T22:30:29+00:00 Sheogorath 2019-05-30T22:27:56+00:00 4da68597f701376307fe8849ed57edd3a80833ed 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> 
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>
Update error message text checks 2018-11-16T22:53:50+00:00 Carles Bruguera 2018-11-06T18:07:28+00:00 5da10c0e2c00a7e26f4521e45888840d41175a61 Signed-off-by: Carles Bruguera <carlesba@gmail.com> 
Signed-off-by: Carles Bruguera <carlesba@gmail.com>
Extend migration error handling 2018-09-05T15:19:35+00:00 Sheogorath 2018-09-05T14:08:32+00:00 81e3d7bd00686b5e4d1e0b53db3eca9901c183c1 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> 
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>
Add missing catch blocks for migration from 1.1.1 to 1.2.0 2018-07-31T06:19:57+00:00 Hugo Caloto 2018-07-09T07:27:17+00:00 26a14dd987b2021f7652bf14da83046eeca2dd6c Signed-off-by: Hugo Caloto <hcaloto@gmail.com> 
Signed-off-by: Hugo Caloto <hcaloto@gmail.com>