The globals option only gated importActual/requireActual in call_member_chain. Other methods (mock, doMock, importMock, etc.) in handle_rstest_method_call ignored this option, causing inconsistent behavior where globals: false would still transform global rs/rstest usage.

Changes

• Added global variable check at entry to handle_rstest_method_call using parser.is_variable_defined()
• Skip processing when identifier is global and globals: false
• Applies consistently to: mock, mockRequire, doMock, doMockRequire, importMock, requireMock, unmock, doUnmock, resetModules, hoisted

Behavior

// Before: globals: false only affected importActual/requireActual
rs.mock('./foo')      // ❌ Still transformed (inconsistent)
rs.importActual('./foo')  // ✅ Skipped (as expected)

// After: globals: false affects all methods
rs.mock('./foo')      // ✅ Skipped (consistent)
rs.importActual('./foo')  // ✅ Skipped (consistent)

// ESM imports always processed regardless of globals setting
import { rs } from '@rstest/core'
rs.mock('./foo')      // ✅ Transformed (both before and after)

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.