From b948c97682dd949b0d216c41ea74f43e6dfe9ba4 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 5 Jan 2022 19:44:39 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index c8fc5163..ed60c968 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -31,23 +31,10 @@ docs cleanup # OUTSTANDING MAJOR AREAS TO BETA - Features - TEST MODE - comment out or put in a debug block all - internal static bool AYANOVA_SERVER_TEST_MODE { get; set; } - internal static decimal AYANOVA_SERVER_TEST_MODE_TZ_OFFSET { get; set; } - internal static string AYANOVA_SERVER_TEST_MODE_SEEDLEVEL { get; set; } - - this: - //CONTENTROOTPATH - //** Not intended for end users - internal static string AYANOVA_CONTENT_ROOT_PATH { get; set; } //Note: set in startup.cs, not in program.cs as it requires startup IHostingEnvironment - - - trial / seeder system - For beta I don't think this is particularly critical, users will likely jump straight to migration anyway no matter what we tell them to do docs see docs section below for beta docs issues Important to go through all existing docs and cleanup re-read every single page and put under construction if not ready yet + Find things that *must* be present for beta testers like how to use controls etc dashboard widgets Not the highest priority for BETA but there shoudl be at least a couple so that feature can be tested also it shoudl at least replicate v7 stuff Just enough an no more, this could be endless, come up with a top 5 or something and limit it to that