Deprecated & replaced BrowserUrl__c fields with new BrowserAddress__c fields #720
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed #696 by making a couple of changes to how the browser's address is captured when logging in lightning components
ComponentLogger
to auto-truncate JS browser fields (includingLogEntryEvent__c.BrowserUrl__c
)public
propertyComponentLogger.ComponentLogEntry.browserUrl
is now deprecated & will be deleted in a future release. It's only intended to be used internally by Nebula Logger, so this hopefully doesn't impact anyone - but mentioning it here, just in case 😉BrowserUrl__c
onLogEntryEvent__e
andLogEntry__c
with new long textarea (2000) fieldsBrowserAddress__c
BrowserUrl__c
fields are too short to store some long URLs (such as URLs with a lot of parameters), and the existing fields can't be converted from text(255) to long text area fields, so new fields are neededBrowserUrl__c
fields will still be populated for foreseeable future (with a truncated value), but they are now considered deprecated - any references in reports, list views, queries, etc. should be updated to use the newBrowserAddress__c
fieldsLogEntryEvent__e
andLogEntry__c