docs: demonstrate UnsafeEntityLogging in todoapp-tutorial server walkthrough (#476) - #487
Merged
Merged
Conversation
This was referenced Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v10.1.0 added the
UnsafeEntityLoggingoption toTableControllerOptions(#446).samples/todoapp-tutorialis the main walkthrough referenced fromdocs/tutorial/client/part-1.mdandpart-2.md([todoapp]), so this updates it to demonstrate the option by enabling sensitive entity logging, following the same pattern already used in thetodoapp-mvcsample (#480 / #485, which demonstrated the securefalsedefault).Changes
samples/todoapp-tutorial/ServerApp/ServerApp.csproj: bumpCommunityToolkit.Datasync.ServerandCommunityToolkit.Datasync.Server.InMemoryfrom10.0.0to10.1.0so the sample builds against the release that introducedUnsafeEntityLogging.samples/todoapp-tutorial/ServerApp/Controllers/TodoItemController.cs: replace the primary-constructor controller with an explicit constructor that wires anILogger<TodoItemController>and setsOptions = new TableControllerOptions { UnsafeEntityLogging = true }, with a comment explaining the security implication (entity contents may contain PII, secrets, or other sensitive business data; only enable when the log sink is secured).Acceptance criteria
samples/todoapp-tutorial/ServerAppenablesUnsafeEntityLogging = trueand wires anILogger.Verification
dotnet restore+dotnet buildonsamples/todoapp-tutorial/ServerApp/ServerApp.csproj— succeeded, 0 warnings/errors.dotnet restore/dotnet buildonDatasync.Toolkit.sln— succeeded (pre-existing, unrelatedNU1903advisories only; the sample is not part of this solution and is unaffected).Closes #476