Nebula Logger: Illegal assignment from List<Schema.PicklistEntry> to List<PicklistEntry> #272
Labels
Type: Bug
Something isn't working
Milestone
Comments
|
Hey @aranwe, thanks for reporting this! Do you know which release your org is currently using? I'm not able to reproduce this error, so I'm wondering if it's possibly related to the new Spring '22 release (assuming that's the version your org is using). |
|
Yup, it's a sandbox with Spring '22 -> it's possible that it's connected, I
was just going through the Release notes and couldn't find any mention of
either PicklistEntry class or anything that seemed related to this in the
Schema namespace.
…On Tue, 18 Jan 2022 at 14:22, Jonathan Gillespie ***@***.***> wrote:
Hey @aranwe <https://github.com/aranwe>, thanks for reporting this! Do
you know which release your org is currently using? I'm not able to
reproduce this error, so I'm wondering if it's possibly related to the new
Spring '22 release (assuming that's the version your org is using).
—
Reply to this email directly, view it on GitHub
<#272 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEQRYSJVWJMYTNBJKNVOGDUWVSQFANCNFSM5MGQWLXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Sounds good, thanks for confirming! I haven't done much testing in a Spring '22 org yet, but I'll see if I can create one & test this issue. It should be a fairly small code change, but I'd like to be able to reproduce the issue before making any code changes. I'll keep you updated on the status, but I have several other bugfixes in-progress, so I'll probably put out another release in a few weeks that contains several bugfixes (including for this issue). |
jongpie
added a commit
that referenced
this issue
Jan 20, 2022
…try> instead of just List<PicklistEntry> I typically include the Schema namespace anyway, not sure why I didn't previously do so in this particular example
jongpie
added a commit
that referenced
this issue
Jan 20, 2022
…try> instead of just List<PicklistEntry> I typically include the Schema namespace anyway, not sure why I didn't previously do so in this particular example
jongpie
added a commit
that referenced
this issue
Mar 11, 2022
[LoggerSettings__c changes] * Closed #279 by adding a new settings field DefaultLogScenario__c and new method Logger.getScenario() * Closed #258 by adding 2 new fields to LoggerSettings__c (IsSavingEnabled__c and IsPlatformEventStorageEnabled__c) * Cleaned up help text in several LoggerSettings__c fields * Added new field LoggerSettings__c.DefaultLogOwner__c that can be used to specify a default owner of Log__c records, using a user ID, username, queue ID or queue developer name * Renamed LoggerSettings__c field StripInaccessibleRecordFields__c to IsRecordFieldStrippingEnabled__c for consistency [Log__c UI changes] * Renamed "View JSON" quickAction to "Open Viewer", and added tabs within logViewer lwc to provide views for both JSON (existing) and log file (new) - a new 'download' button now allows exporting the content to a file - For the unlocked package, the logJSON lwc was renamed back to logViewer * Fixed a conditional render rule on LogEntryRecordpage.flexipage, added an extra check in parseStackTrace() method to handle some problematic lines within a string that is otherwise valid, removed namespace filter when querying ApexClass in LogEntryHandler * Added picklist values for API Versions in calendar year 2022 [Managed Package changes] * Changed visibility of LoggerParameter__mdt object from 'Protected' to 'Public' * Made most LoggerParameter__mdt records non-protected so they can be updated in the managed package * Worked with @jamessimone to implement a custom approach for dynamically retrieving objects & fields (including namespace) in loggerSettings and logEntryEventStream LWCs, using the new Apex class LoggerSObjectMetadata - LWC does not officially support platform events, custom settings, or custom metadata types, so LoggerSObjectMetadata will be used instead * Re-added skeleton of the deprecated quick action ViewJSON and aura cmp logJSONViewer for the managed package [Bugfixes] * Fixed #272 by explicitly delcaring the list as List<Schema.PicklistEntry> instead of just List<PicklistEntry> [Improvements for Tests & Utilities] * Added calls to Test.getEventBus().deliver() in Flow classes to try to resolve some inconsistent test failures in the pipeline * Standardized calls to Database.query() to also use String.escapeSingleQuotes() * Fixed #276 - Added a check in LoggerEmailUtils to check if email deliverability is enabled before sending an email [skip ci] * Refactored some code in LogHandler, removed exclusion of PMD rule 'AvoidGlobalModifier' * Added missing test in LogEntryTagHandler_Tests for updating records * Fixed some test asserts for 'DUPLICATE_VALUE' error that didn't work correctly when the user's language was not English * Updated LoggerTestUtils test method to create its own test user, instead of trying to update the current user's record ## Pipeline & Packaging * Bumped package version to v4.7.0, added devDependencies for outdated packages reported by dependabot in GitHub * Closed #263 by adding new keyword "ancestorVersion": "HIGHEST" in both sfdx-project.json files * Updated mgd pkg creation script to use --codecoverage instead of --skipvalidation * Updated codecov.yml so PR comments are deleted & readded, instead of updated * Fixed error handling of package creation & installation in pwsh scripts * Temporarily disabling pipeline check for updated docs due to an error in apexdocs package * Switched to using JWT bearer flow in pipeline for dev hub auth * Upgraded sfdx-cli, cleaned up package.json, cleaned up both sfdx-project.json files * Removed local linking of sfdx-scanner in npm prepare script, added linking command to build.yml, added new sfdx plugin for prettier * Moved scripts folder back to being a top-level folder * Switched to using new packageAlias sorting feature in bummer sfdx plugin * Switched from using sfdx force:community:create + a delay in the pipeline, to instead deploying metadata for a skeleton Experience Cloud site The pipeline has been having inconsistent failures because it previously had a 2 minute delay added to wait for force:community:create, but sometimes it took Salesforce longer to finish creating the site asynchronously. Using a deploy will make it a synchronous operation, so it should prevent the inconsistent failures. Co-authored-by: James Simone <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
when trying to install Nebula Logger I get the following error:
I have actually noticed that Salesforce has recently changed the return type of getPicklistValues() and started to throw type mismatch on Schema vs global PicklistEntry.
I can make PR if needed :)
Thank you!
The text was updated successfully, but these errors were encountered: