Skip to content

fix: main does not build — the MeshWeaver.AI using was restored TWICE #2416

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rbuergi wants to merge 1 commit into from
Closed

fix: main does not build — the MeshWeaver.AI using was restored TWICE #2416

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions memex/Memex.Portal.Shared/Api/MeshApiEndpoints.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,11 @@
// modules through [assembly: TypeForwardedTo], and a forwarder cannot rename — so the namespace is
// frozen at whatever it was when those modules were built. Do not "tidy" this using to match the
// assembly name; that is what broke main at 17:26.
//
// This import is therefore load-bearing and is NOT an AI-assembly dependency. It was removed as a
// "phantom" in #2349 and restored twice independently (#2408 and #2411) — once with this banner and
// once inline further down, which is how main ended up with the SAME using twice and CS0105 under
// warnings-as-errors. One directive, one explanation: keep them together.
Comment on lines +9 to +10
using MeshWeaver.AI;
using MeshWeaver.Mesh;
using System.Reactive.Linq;
Expand All @@ -12,11 +17,6 @@
using MeshWeaver.Hosting.AspNetCore; // SessionHubResolver, McpConfiguration
using MeshWeaver.Mesh.Security; // WellKnownUsers
using MeshWeaver.Mesh.Services;
using MeshWeaver.AI; // MeshOperations — the TYPE ships in
// MeshWeaver.Mesh.Operations, but its namespace is a
// FROZEN binary contract (#2370), so this import is
// load-bearing and is NOT an AI-assembly dependency.
// Removed as a 'phantom' in #2349 and restored here.
using MeshWeaver.Messaging; // AccessService
using Memex.Portal.Shared.Authentication;
using Microsoft.AspNetCore.Builder;
Expand Down
Loading