@suss/adapter-python 0.20.0 → 0.21.1

package/dist/index.d.cts

@@ -158,6 +158,15 @@ interface DecoratorClassification {
      * resolved there, since that is where the namespace is constructed.
      */
     objectModule?: ModuleBinding;
+    /**
+     * The call the rules say built the object this decorator hangs on, when
+     * the lexical scope could not say. A router prefix is looked up by this
+     * call rather than by a variable name, because there may not be one.
+     */
+    subjectConstruction?: {
+        key: string;
+        constructorName: string;
+    };
 }
 declare function classifyDecorator(decoratorNode: Node, scope: Scope): DecoratorClassification;
 
@@ -470,6 +479,12 @@ type RoutePrefixResolution = {
 };
 interface RouterIndex {
     resolve(pattern: PythonDiscoveryPattern, module: ModuleBinding, objectName: string): RoutePrefixResolution;
+    /**
+     * The same answer for a decorator whose object has no variable name to
+     * look up, such as one written on `self.router`. The rules give the call
+     * that built it, and every construction is already keyed by its call.
+     */
+    resolveConstruction(pattern: PythonDiscoveryPattern, module: ModuleBinding, constructorName: string, constructionKey: string): RoutePrefixResolution;
     /**
      * The module-level def a name in another module refers to, with that
      * module's own bindings, so a decorator written through a project wrapper
@@ -515,6 +530,8 @@ interface DiscoveryOptions {
     storage?: StorageLookup | undefined;
     /** The file's absolute path, which module resolution wants; `filePath` may be shortened for display. */
     absoluteFile?: string | undefined;
+    /** The project's facts, so the rules can say what an object no scope has a binding for was built by. */
+    facts?: Database | undefined;
 }
 declare function discoverUnits(root: Node, module: ModuleBinding, options: DiscoveryOptions): RawCodeStructure[];
 

package/dist/index.d.ts

@@ -158,6 +158,15 @@ interface DecoratorClassification {
      * resolved there, since that is where the namespace is constructed.
      */
     objectModule?: ModuleBinding;
+    /**
+     * The call the rules say built the object this decorator hangs on, when
+     * the lexical scope could not say. A router prefix is looked up by this
+     * call rather than by a variable name, because there may not be one.
+     */
+    subjectConstruction?: {
+        key: string;
+        constructorName: string;
+    };
 }
 declare function classifyDecorator(decoratorNode: Node, scope: Scope): DecoratorClassification;
 
@@ -470,6 +479,12 @@ type RoutePrefixResolution = {
 };
 interface RouterIndex {
     resolve(pattern: PythonDiscoveryPattern, module: ModuleBinding, objectName: string): RoutePrefixResolution;
+    /**
+     * The same answer for a decorator whose object has no variable name to
+     * look up, such as one written on `self.router`. The rules give the call
+     * that built it, and every construction is already keyed by its call.
+     */
+    resolveConstruction(pattern: PythonDiscoveryPattern, module: ModuleBinding, constructorName: string, constructionKey: string): RoutePrefixResolution;
     /**
      * The module-level def a name in another module refers to, with that
      * module's own bindings, so a decorator written through a project wrapper
@@ -515,6 +530,8 @@ interface DiscoveryOptions {
     storage?: StorageLookup | undefined;
     /** The file's absolute path, which module resolution wants; `filePath` may be shortened for display. */
     absoluteFile?: string | undefined;
+    /** The project's facts, so the rules can say what an object no scope has a binding for was built by. */
+    facts?: Database | undefined;
 }
 declare function discoverUnits(root: Node, module: ModuleBinding, options: DiscoveryOptions): RawCodeStructure[];