Debugger tool references schema.<SObject> when debugging trigger with the same name as the SObject

Issue #2395 resolved
John De Santiago created an issue

When a trigger exists with the same name as an SObject (e.g., Account.trigger), the step debugger opens and steps through the schema object file (e.g., Account) rather than the trigger file.

How to reproduce:

  1. Create a trigger on an Account object and name it “Account”.
  2. Add some code to the trigger class so that you can attempt to step through it in the debugger
  3. Create a test class that creates an Account record so that it invokes the Account trigger
  4. Run the unit test using the debugger
  5. As you step through, you should notice that it opens the Schema.Account file rather than the Account.trigger file

Comments (2)

  1. Log in to comment