17 Commits (ef533015ae8d2da48848cd97f847b4764bf13c57)

Author	SHA1	Message	Date
Mark Monteiro	1666f3ca14	Use dependency injection to construct migration routines	4 years ago
Mark Monteiro	9e89cbbc3a	Store migration names alongside Ids in configuration in order to assist with development/debugging	4 years ago
Mark Monteiro	72bf920291	Use a Guid to uniquely identify migrations instead of a string name ... Also use a list instead of an array to store executed migrations in the configuration class	4 years ago
Mark Monteiro	2f0b4cc24c	Clean up migration logging messages	4 years ago
Mark Monteiro	a0fdceb4bc	Throw exception on migration failure to halt application ... Also save migration configuration after each migration instead of at the end in case an exception is thrown part way through the list	4 years ago
Joshua M. Boniface	ae9948ce04	Merge branch 'master' into logging-migration	4 years ago
Mark Monteiro	1295f6c79b	Documentation and log message cleanup	4 years ago
Mark Monteiro	7ecb16a46e	do not ignore exceptions during migration execution	4 years ago
Mark Monteiro	4c2b543b30	Rename IUpdater to IMigrationRoutine	4 years ago
Mark Monteiro	1a9908d094	Add migration to create "logging.user.json"	4 years ago
Vasily	5a0f1fe848	Implement review suggestion	4 years ago
Vasily	098d3538e3	Disable logging.json migration as it is not ready yet	4 years ago
Vasily	d4564d8e29	More logging, mark all migrations as applied if setup wizard is not complete	4 years ago
Vasily	55b429e5e8	Moved migration routines to their own directory	4 years ago
Vasily	ccafebca68	Extract "migrations" config name to a proper constant	4 years ago
Vasily	ecaa7f8014	Improve migration logic	4 years ago
Vasily	66e11879ef	Shuffle migrations in a more manageable structure	4 years ago