Bugfix: Name Shadowing Issues for Several Schema Apex Classes

Thanks to @amp42 for reporting this bug!

Core Unlocked Package Changes

Switched Using Fully-Qualified Class Names in the Schema Namespace

• Fixed #584 (reported by @amp42) by switching to using fully-qualified Apex class references to several classes in the Schema namespace, like Schema.User, to avoid collision issues in orgs that use name-shadowing classes. These class references are now fully-qualified throughout the codebase. This is the same concept & approach as the changes made in v4.9.0, v4.9.4, and v4.9.6 to fully-qualify references to classes & enums in the System namespace

  • Schema.Account (these references are only used for tests & sample recipes, not in Nebula Logger's core code)
  • Schema.AuthSession
  • Schema.LoginHistory
  • Schema.Network
  • Schema.Organization
  • Schema.Profile
  • Schema.Topic
  • Schema.TopicAssignment
  • Schema.User

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.12.4...v4.12.5

• SF CLI: sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001Mk5PQAS
• SFDX CLI: sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001Mk5PQAS
• Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5Y000001Mk5PQAS
• Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t5Y000001Mk5PQAS