You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Encapsulation leak: users.ts directly imports ExtractRoutesFromAPI from ApiClass.ts #43051
In the server API subsystem, apps/meteor/server/api/api.ts acts as the public API gateway/entry point, while apps/meteor/server/api/ApiClass.ts contains the internal implementation details of the API class.
Currently, route definition modules like apps/meteor/server/api/v1/users.ts import API from api.ts, but simultaneously bypass this public gateway to import internal type helpers like ExtractRoutesFromAPI directly from ApiClass.ts.
This creates an architectural bypass edge and violates encapsulation boundaries: consumers should consume public types and instances exclusively through the gateway/public facade rather than reaching into back-office class implementation files.
Current Behavior
In apps/meteor/server/api/v1/users.ts:
importtype{ExtractRoutesFromAPI}from'../ApiClass';// ⚠️ Bypassing public API moduleimport{API}from'../api';// Using public gateway
Activity