Tidy stale studio-web comment on the IO csproj#2
Merged
Conversation
The original net8.0-only justification cited a planned studio-web WASM consumer at net10.0. That plan was dropped; Studio remains the primary client. The new comment reflects current reality: the IO library is authoring/build-time only, and the Unity package consumes its export outputs, not its types. No build or behaviour change.
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
1 participant
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
The
net8.0-only justification onOpenApparatus.IO.csprojcited a plannedstudio-webWASM consumer atnet10.0. That plan was dropped — Studio remains the primary client. The new comment reflects current reality: the IO library is authoring/build-time only, and the Unity package consumes its export outputs (not its types), so nonetstandard2.1target is needed.Comment-only change. 1 file, +3 / -4. No build or behaviour change.
Test plan
dotnet buildstill succeeds (no functional change, so this should be automatic).