Feat button for cicd testing

.gitignore

@@ -198,4 +198,8 @@ CHANGELOG.md
 
 
 /AllTestResults/coverage.cobertura.xml
-/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/Logs/*.txt
+/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/Logs/*.txt
+/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/wwwroot/appsettings.json
+/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/wwwroot/appsettings.ci.json
+/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/wwwroot/appsettings.Development.json
+/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/wwwroot/appsettings.Production.json

CHANGELOG.md

@@ -1,19 +1,6 @@
-# [1.5.0](https://github.com/TechnologyEnhancedLearning/TELBlazor/compare/v1.4.0...v1.5.0) (2025-05-30)
+# [1.6.0-feat-button-for-cicd-testing.1](https://github.com/TechnologyEnhancedLearning/TELBlazor/compare/v1.5.0...v1.6.0-feat-button-for-cicd-testing.1) (2025-06-06)
 
 
 ### Features
 
-* **button:** changelog ([9156eb6](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/9156eb69b632ba7d661e1502f024c8f2e72f2f32))
-* **button:** order of running error ([91c3b77](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/91c3b77014c255b0755f7a43be646efcc2e0af97))
-* **button:** readme setup ([8d440f2](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/8d440f2457c82c46b012e48fab7c3d8bb0ddb2e2))
-* **button:** removing everything that is now ignored ([7153a84](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/7153a84b31513729099ed2ae2207ff77a7f746c4))
-
-# [1.5.0-feat-button-for-cicd-testing.1](https://github.com/TechnologyEnhancedLearning/TELBlazor/compare/v1.4.0...v1.5.0-feat-button-for-cicd-testing.1) (2025-05-29)
-
-
-### Features
-
-* **button:** changelog ([9156eb6](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/9156eb69b632ba7d661e1502f024c8f2e72f2f32))
-* **button:** order of running error ([91c3b77](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/91c3b77014c255b0755f7a43be646efcc2e0af97))
-* **button:** readme setup ([8d440f2](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/8d440f2457c82c46b012e48fab7c3d8bb0ddb2e2))
-* **button:** removing everything that is now ignored ([7153a84](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/7153a84b31513729099ed2ae2207ff77a7f746c4))
+* **button:** nav ([075d01f](https://github.com/TechnologyEnhancedLearning/TELBlazor/commit/075d01f3aa5a60afd55ac96f6fd1d257a344c302))

PackageSettings.props.local.template

@@ -3,7 +3,9 @@
 	<PropertyGroup>
 
 		<!--your local system environment variables-->
-		<TELBlazorPackageSource>$(LocalPackagePath)</TELBlazorPackageSource>
+		<TELBlazorPackageSource>$(TELBlazorPackageSource)</TELBlazorPackageSource>
+		<!--<TELBlazorPackageSource>$(LocalPackagePath)</TELBlazorPackageSource>-->
+		<!--<TELBlazorPackageSource>$(TELPackageSource)</TELBlazorPackageSource>-->
 		<NupkgOutputPath>$(LocalPackagePath)</NupkgOutputPath>
 
 		<!--for faster iteration-->

README.md

@@ -87,6 +87,10 @@ It is client side so the users browser will do the work.
 	- Bonus (you could do this while cloning): if you don't want to wait for the pipeline to fail your commit names and for pushes to accidently expose your secrets: you may want to add
 		- gitguardian from confluence docs (follow it to the letter) [gitguardian global setup instructions](https://hee-tis.atlassian.net/wiki/spaces/TP/pages/3855253505/GitGuardian+Setup+-+Simplified+Version)
         - and add a pre-commit and push hook (you need both as you cannot lint what hasnt yet been commit) you can add these to your git templates if you want them for every repo, or just to this repos pre- push- commits, or you can be lazy and add them into the gitguardian hook
+		- you will need git commitlint globally (angular because it goes with the versioning tool for repo versioning)
+			```
+				npm install -g @commitlint/cli @commitlint/config-angular
+			```
 		-	```
 				#### --- Commitlint Logic (force local config) ---
 				REPO_ROOT=$(git rev-parse --show-toplevel)
@@ -242,6 +246,8 @@ dotnet nuget add source "https://nuget.pkg.github.com/TechnologyEnhancedLearning
   --store-password-in-clear-text
 ````
 
+Note: You may also wish to go into your user appdata or roaming and find your global nuget config and add the credentials in there. Do this by copying the 
+TELPackage part of the config but with the system environment variable values you set earlier. This will mean LH for example will be able to access TEL packages and so will other projects.
 
 #### Create appsettings
 *Be aware that because WASM code is in the browser appsettings in the wasm client projects are not secret and sensitive data should not go in them*

TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/Program.cs

@@ -52,7 +52,7 @@
     .CreateLogger();
 
 // Add Serilog to logging providers
-builder.Logging.AddSerilog(Log.Logger, dispose: true);
+builder.Logging.AddSerilog(Log.Logger, dispose: true);//qqqq may not need dispose for client
 
 //for really bad fails
 try
@@ -71,7 +71,7 @@
     builder.Services.AddBlazoredLocalStorage();
 
     //Scoped because being consumed with storage where singleton doesnt survive mvc page teardown
-    builder.Services.AddScoped<LoggingLevelSwitch>(sp => levelSwitch);
+    //qqqq do we need it builder.Services.AddScoped<LoggingLevelSwitch>(sp => levelSwitch);
     builder.Services.AddScoped<ILogLevelSwitcherService, SerilogLogLevelSwitcherService>();
     builder.Services.AddScoped(sp => new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) });
 

TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/Properties/launchSettings.template.json

@@ -0,0 +1,23 @@
+{
+  "profiles": {
+    "TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client": {
+      "commandName": "Project",
+      "launchBrowser": true,
+      "inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
+      "applicationUrl": "https://localhost:7210;http://localhost:5193",
+      "environmentVariables": {
+        "ASPNETCORE_ENVIRONMENT": "Development"
+      }
+      //},
+      //"TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client.CI": {
+      //  "commandName": "Project",
+      //  "launchBrowser": true,
+      //  "inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
+      //  "applicationUrl": "https://localhost:7210;http://localhost:5193",
+      //  "environmentVariables": {
+      //    "ASPNETCORE_ENVIRONMENT": "ci"
+      //  }
+      }
+    }
+  }
+}

TELBlazor.Components.ShowCase.E2ETests.WasmServerHost/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client/TELBlazor.Components.ShowCase.E2ETests.WasmServerHost.Client.csproj

@@ -11,6 +11,10 @@
 	<Configurations>Debug;Release;ci</Configurations>
 
   </PropertyGroup>
+
+  <ItemGroup>
+    <Content Remove="Properties\launchSettings.template.json" />
+  </ItemGroup>
 	<ItemGroup>
 		<!-- Logging -->
 		<PackageReference Include="Serilog" />

TELBlazor.Components.ShowCase.Shared/Layouts/ComponentLayouts/ComponentNavMenu.razor

@@ -1,7 +1,10 @@
 <nav class="app-side-nav">
-    <h2 class="app-side-nav__heading">TELBlazor Components</h2>
+    <h2 class="app-side-nav__heading">Site Navigation</h2>
     <ul class="nhsuk-list app-side-nav__list">
         <li class="app-side-nav__item"><NavLink class="app-side-nav__link" href="./" Match="NavLinkMatch.All">Home</NavLink></li>
+    </ul>
+    <h2 class="app-side-nav__heading">TELBlazor Components</h2>
+    <ul class="nhsuk-list app-side-nav__list">
         <li class="app-side-nav__item"><NavLink class="app-side-nav__link" href="TELButton">TELButton</NavLink></li>
     </ul>
     <h2 class="app-side-nav__heading">Test Components</h2>

TELBlazor.Components.ShowCase.Shared/Pages/ComponentPages/TestComponentPages/LogLevelSwitcherPage.razor

@@ -11,6 +11,6 @@
 @code {
     private bool IsTestComponent => true;
     private string Title => "LogLevelSwitch";
-    private string Instructions => "Open the console and change the log levels, view other components and see their logging change";
-    private string Description => "This is a test component: Changing the log level does not trigger events because everything would need one so it will affect new components.  Also we have complete tare down between mvc components so local storage for 24 hours or db user logging state would be needed the singleton will not be enough. For implementation into MVC see MVCBlazor project. In production the value of this would be being able to programmatically change the loglevel in a browser based on an event for example a recurring problem. Another potential use is giving an admin or console option so a user being supported with an error could increase logging, or staff reporting a bug could ensure they are creating logs whilst reporting a bug such that they could turn up logging, trigger an error, and share when they successfully repeated the error. Sometimes logging is used for analytics but specific analytics tools are better for this.or to change the loglevel for a user who is supported via a tool. So this component would be the starting point for easily changing loglevel live.";
+    private string Instructions => "Open the console and change the log levels, view other components and see their logging change. Look in application storage. ";
+    private string Description => "This is a test component: Changing the log level does not trigger events because everything would need one so it will affect new components. E.g. If you increase the loglevel components on the screen wont change logging behaviour until rerendered.  Also we have complete tare down between mvc components so local storage for 24 hours or db user logging state would be needed the singleton will not be enough. For implementation into MVC see MVCBlazor project. In production the value of this would be being able to programmatically change the loglevel in a browser based on an event for example a recurring problem. Another potential use is giving an admin or console option so a user being supported with an error could increase logging, or staff reporting a bug could ensure they are creating logs whilst reporting a bug such that they could turn up logging, trigger an error, and share when they successfully repeated the error. Sometimes logging is used for analytics but specific analytics tools are better for this.or to change the loglevel for a user who is supported via a tool. So this component would be the starting point for easily changing loglevel live. Serilog is needed for dynamic changing of logging and is a better fit with blazor generally but ilogger interface is used so that serilog is not required. Currently it does not post logs to an api, so only the client is aware of them.";
 }