Method extractMapper

src/extraction/mybatis-extractor.ts:170–255

(
    fileNodeId: string,
    namespace: string,
    dialect: 'mybatis' | 'ibatis',
    bodyStart: number,
    bodyEnd: number
  )

  }

  private extractMapper(
    fileNodeId: string,
    namespace: string,
    dialect: 'mybatis' | 'ibatis',
    bodyStart: number,
    bodyEnd: number
  ): void {
    const body = this.source.slice(bodyStart, bodyEnd);
    // Match each top-level statement-shaped element. The body may have nested
    // tags (`<if>`, `<foreach>`, `<include>`), so we scan with a regex that
    // pairs an opening tag to its matching close — the simple form below works
    // because MyBatis/iBatis statement elements are not themselves nested.
    // iBatis 2 adds the generic `<statement>` and `<procedure>` on top of the
    // MyBatis 3 verbs; gating by dialect keeps MyBatis extraction unchanged.
    const verbs =
      dialect === 'ibatis'
        ? 'select|insert|update|delete|sql|statement|procedure'
        : 'select|insert|update|delete|sql';
    const stmtRegex = new RegExp(`<(${verbs})\\b([^>]*)>([\\s\\S]*?)</\\1>`, 'g');
    let m: RegExpExecArray | null;
    while ((m = stmtRegex.exec(body)) !== null) {
      const elemType = m[1]!;
      const attrs = m[2] ?? '';
      const elemBody = m[3] ?? '';
      // Accept either quote style (`(["'])…\1`). The identifier-shaped MyBatis
      // attributes matched here and below (namespace/id/refid/resultType/
      // parameterType) are Java FQNs, method names, or type aliases and never
      // contain a quote character, so excluding both quotes from the value is safe.
      const idMatch = /\bid\s*=\s*(["'])([^"']+)\1/.exec(attrs);
      if (!idMatch) continue;
      const id = idMatch[2]!;
      const absoluteIndex = bodyStart + m.index;
      const startLine = this.getLineNumber(absoluteIndex);
      const endLine = this.getLineNumber(absoluteIndex + m[0].length);
      const { qualifiedName: qualified, name } = this.qualifyStatement(namespace, id);
      const isSqlFragment = elemType === 'sql';
      // The id-hash folds in the statement's byte offset (unique per statement
      // in the file), not just the start line: two statements sharing a
      // qualifiedName AND a start line — e.g. a vendor-split `databaseId` pair
      // (`<select id="x" databaseId="oracle">…</select><select id="x"
      // databaseId="mysql">…`) written on one line — would otherwise hash to
      // the same node id, and `INSERT OR REPLACE INTO nodes` (id is the PRIMARY
      // KEY) would silently drop one. qualifiedName and startLine are stored
      // unchanged, so the Java↔XML suffix-match bridge is untouched.
      const nodeId = generateNodeId(this.filePath, 'method', qualified, absoluteIndex);
      const node: Node = {
        id: nodeId,
        kind: 'method',
        name,
        qualifiedName: qualified,
        filePath: this.filePath,
        language: 'xml',
        signature: this.buildSignature(elemType, attrs, isSqlFragment),
        startLine,
        endLine,
        startColumn: 0,
        endColumn: 0,
        docstring: this.previewSql(elemBody),