v4.16.4 - Bugfix: logger LWC Initialization Message #888
jongpie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Core Unlocked Package Changes
Fixed #870 (reported by @dominykasvitkus) by updating the
loggerLWC initialization message to only print when JavaScript console logging is enabled viaLoggerSettings__c. Also resolved some test isolation issues inlogger.test.js+ test improvements + code cleanup:loggerService.jsto only callconsole.info()with an init message ('logger component initialized') when console logging is enabled viaLoggerSettings__c.IsJavaScriptConsoleLoggingEnabled__cenableSystemMessages()anddisableSystemMessages()inloggerService.jswith a new static variableLoggerService.areSystemMessagesEnabled(intended for internal-use only)logger.test.jsto resetLoggerService.hasInitializedandLoggerService.areSystemMessagesEnabledstatic variables inbeforeEach()(instead ofafterAll())jest.resetAllMocks()instead ofjest.clearAllMocks()inlogger.test.jsfor better test isolationcreateLogger,getLogger, andgetMarkupLogger)Also include a 🤏 liiiiiiitle bit of scope creep:
codecov.ymlto compensate for the lower code coverage in LWC tests for now (currently around ~86%). Eventually, tests & code coverage for LWC will be improved - but for now, the constant pipeline alerts from codecov.io aren't particularly helpful 😅LogBatchPurgerusing the null coalescing operator (??) to reduce the lines of code neededLoggerScenarioRule__mdt.IsLogAssignmentEnabled__cto use the termLogger Scenario, instead of the deprecated termLog ScenarioInstallation Info
CoreUnlocked Package - no namespaceFull Changelog: v4.16.3...v4.16.4
sf package install --wait 20 --security-type AdminsOnly --package 04tKe0000011MyWIAUThis discussion was created from the release v4.16.4 - Bugfix: logger LWC Initialization Message.
Beta Was this translation helpful? Give feedback.
All reactions