You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the unlocked package does not have a namespace, orgs can encounter installation errors for Nebula Logger if the target org has any custom Apex code (classes, enums, interfaces, etc.) with the same name as standard class in the Schema or System namespace (referred to as name shadowing).
This is the same concept & approach as the changes made in several previous releases (listed below) - but my hope is that this PR finally finishes this effort, and all references are now fully qualified.
This shouldn't cause any functional changes to Nebula Logger - this is to tidy up existing references to avoid name collisions so that more orgs can use the unlocked package.
Core Unlocked Package Changes
Apex Code Changes
Switched to using fully-qualified references for these standard classes in the Schema and System namespaces :
cleanupconfigurationsItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typelog managementItems related to the custom objects & Logger Console applogger engineItems related to the core logging engineunlocked packageIssues and enhancements that specifically apply to the unlocked package
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Since the unlocked package does not have a namespace, orgs can encounter installation errors for Nebula Logger if the target org has any custom Apex code (classes, enums, interfaces, etc.) with the same name as standard class in the
Schema
orSystem
namespace (referred to as name shadowing).This is the same concept & approach as the changes made in several previous releases (listed below) - but my hope is that this PR finally finishes this effort, and all references are now fully qualified.
v4.9.0
v4.9.4
v4.9.6
v4.12.5
This shouldn't cause any functional changes to Nebula Logger - this is to tidy up existing references to avoid name collisions so that more orgs can use the unlocked package.
Core Unlocked Package Changes
Apex Code Changes
Switched to using fully-qualified references for these standard classes in the
Schema
andSystem
namespaces :Schema
namespace standard classesApexClass
→Schema.ApexClass
ApexEmailNotification
→Schema.ApexEmailNotification
ApexTrigger
→Schema.ApexTrigger
AsyncApexJob
→Schema.AsyncApexJob
BatchApexErrorEvent
→Schema.BatchApexErrorEvent
CustomPermission
→Schema.CustomPermission
DisplayType
→Schema.DisplayType
FlowDefinitionView
→Schema.FlowDefinitionView
FlowExecutionErrorEvent
→Schema.FlowExecutionErrorEvent
FlowVersionView
→Schema.FlowVersionView
PermissionSet
→Schema.PermissionSet
PermissionSetAssignment
→Schema.PermissionSetAssignment
SoapType
→Schema.SoapType
UserRecordAccess
→Schema.UserRecordAccess
UserRole
→Schema.UserRole
System
namespace standard classesBatchableContext
→System.BatchableContext
Comparable
→System.Comparable
Database
→System.Database
EventBus
→System.EventBus
FinalizerContext
→System.FinalizerContext
InstallHandler
→System.InstallHandler
JSON
→System.JSON
Matcher
→System.Matcher
Pattern
→System.Pattern
PicklistEntry
→System.PicklistEntry
Queueable
→System.Queueable
QueueableContext
→System.QueueableContext
Quiddity
→System.Quiddity
Request
→System.Request
RestContext
→System.RestContext
RestRequest
→System.RestRequest
RestResponse
→System.RestResponse
Schedulable
→System.Schedulable
SchedulableContext
→System.SchedulableContext
Search
→System.Search
TriggerOperation
→System.TriggerOperation
UUID
→System.UUID
Scope creep: fixed some flaky tests in
LogBatchPurgeController_Tests
extra-tests
Metadata Changesextra-tests
directory to be in separate subdirectories (one for each namespace,Schema
andSystem
)Schema
&System
references (mentioned above) that are now using fully-qualified referencesInstallation Info
Core Unlocked Package - no namespace
Full Changelog: v4.13.12...v4.13.13
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y0000015oDsQAI
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y0000015oDsQAI
This discussion was created from the release Improved Fully-Qualified References.
Beta Was this translation helpful? Give feedback.
All reactions