Created 10 detailed GitHub issues covering: - Project activation and management UI (#1-2) - Worker node coordination and visualization (#3-4) - Automated GitHub repository scanning (#5) - Intelligent model-to-issue matching (#6) - Multi-model task execution system (#7) - N8N workflow integration (#8) - Hive-Bzzz P2P bridge (#9) - Peer assistance protocol (#10) Each issue includes detailed specifications, acceptance criteria, technical implementation notes, and dependency mapping. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
29 lines
1.0 KiB
TypeScript
29 lines
1.0 KiB
TypeScript
import type FileState from '../FileState.js';
|
|
import type { ComponentNodePath, ResolverClass } from './index.js';
|
|
interface FindExportedDefinitionsResolverOptions {
|
|
limit?: number;
|
|
}
|
|
/**
|
|
* Given an AST, this function tries to find the exported component definitions.
|
|
*
|
|
* The component definitions are either the ObjectExpression passed to
|
|
* `React.createClass` or a `class` definition extending `React.Component` or
|
|
* having a `render()` method.
|
|
*
|
|
* If a definition is part of the following statements, it is considered to be
|
|
* exported:
|
|
*
|
|
* modules.exports = Definition;
|
|
* exports.foo = Definition;
|
|
* export default Definition;
|
|
* export var Definition = ...;
|
|
*
|
|
* limit can be used to limit the components to be found. When the limit is reached an error will be thrown
|
|
*/
|
|
export default class FindExportedDefinitionsResolver implements ResolverClass {
|
|
limit: number;
|
|
constructor({ limit }?: FindExportedDefinitionsResolverOptions);
|
|
resolve(file: FileState): ComponentNodePath[];
|
|
}
|
|
export {};
|