-
-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Summer '24 Release (API v61.0) - v4.14.0 #700
Conversation
b27db1d
to
db4b7e6
Compare
db4b7e6
to
8e49729
Compare
With all due respect is there any specific date on the release? |
@Ben-Nathan-CTM I am currently collaborating with a few teams/companies to try to finalize the scope of changes that will be included in |
5a529b8
to
8b023d9
Compare
d9e5a93
to
66334de
Compare
… (not in the pipeline or when creating package versions) It includes the feature 'EinsteinGPTPlatform', which I've been trying out when writing Apex. It also gives an easy way to enable other features/settings that could be useful for dev, but not needed by any of Nebula Logger's functionality. Also renamed the existing scratch def files to have a 'build-' prefix Some org settings that were previously configured via scratch def files are now stored as metadata in a new 'dev' directory (which is now the default directory in sfdx-project.json)
…s://mob.sh) with Nebula Logger
…d reverted to only using LogEntry__c.LoggingLevel__c The emojis shown in LoggingLevelWithImage__c have now been added to the labels of the picklist values in the global value set LoggingLevel
…ts, HTTP responses, REST request, and REST responses
66334de
to
dd94d11
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #700 +/- ##
==========================================
- Coverage 95.39% 95.37% -0.02%
==========================================
Files 51 51
Lines 5645 5648 +3
==========================================
+ Hits 5385 5387 +2
- Misses 260 261 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…consolidated its contents to instead be part of the tab "Related Records"
c5026f1
to
0ee2384
Compare
Core Unlocked Package Changes
Bumped all metadata to API v61.0 (Summer '24 release)
Resolved Make Log and Log Entry page tabs conditionally visible based on logged data #697 by updating
LogEntryRecordPage
andLogRecordPage
flexipages to conditionally display tabs (tab-visibility functionality was added in Salesforce's Summer '24 release)LogEntryRecordPage
& consolidated its contents to instead be part of the tab "Related Records". This keeps all of the fields related toSObject
data grouped together.Added 5 new list views on
LogEntry__c
All Exception Log Entries
All HTTP Request Log Entries
All HTTP Response Log Entries
All REST Request Log Entries
All REST Response Log Entries
Deprecated the formula field
LogEntry__c.LoggingLevelWithImage__c
, and reverted to only usingLogEntry__c.LoggingLevel__c
. The emojis shown inLoggingLevelWithImage__c
have now been added to the labels of the picklist values in the global value setLoggingLevel
.LoggingLevelWithImage__c
is a formula field that was introduced as part of releasev4.0.0
(PR Roll-up and reporting fields streamlined #76) that originally used Salesforce-provided flag images (red, orange, & green) to indicate the severity of each log entryv4.9.3
(PR New indicator icons #408), the original flag images were replaced with emojis inLoggingLevelWithImage__c
, which were then further updated in releasev4.13.9
LoggingLevel__c
, it still provides the same visual indicator asLoggingLevelWithImage__c
when viewingLogEntry__c
records, butLoggingLevel__c
provides a meaningful sort order in list views, queries, etc. - sorting onLoggingLevelWithImage__c
doesn't provide a very meaningful sort orderLoggingLevel__c
, which will automatically be changed for orgs upgrading versions of the unlocked package. But for orgs using the managed package, the list views will not be automatically updated, you will need to manually update the list views' selected fields (if desired).Fixed assertion failure for it_should_return_user_search_results_list_when_matches_found test method #688 by updating
LoggerSettingsController_Tests
to callLogManagementDataSelector.getInstance().getUsersByNameSearch()
, instead of duplicating the queryUpdated the descriptions of the 4 included permission sets to clarify what each one provides
Code cleanup (internal use only): Updated
public
instance methodLogEntryEventBuilder.setTimestamp()
to use a fluent API, and streamlined the existing usages ofsetTimestamp()
in several other classes by updating to use the fluent APIPipeline & Dev Changes
nebula-logger/extra-tests/tests/LogEntryEventHandler_Tests_FieldMappings.cls
sf
CLI environment variables tobuild.yml
to disable checking for updates during pipeline runssf
CLI is periodically upgraded in the repo, there's no need for the pipeline to check during every runconfig/scratch-orgs/dev-scratch-def.json
that will only be used for development (not in the pipeline or when creating package versions)path
tosfdx-project.json
fornebula-logger/dev/
to store some extra metadata that's used during dev. This metadata doesn't impact Nebula Logger directly & is not included in Nebula Logger's packagessfdx-project.json
for creating/retrieving new metadata.mob
file to the project root - this provides some defaults when using themob
CLI with Nebula Loggermob
CLI isn't necessary at all for working on Nebula Logger, but I sometimes like to use it during development of prototypes