From 056a0d5e89dc05e2a2619b2f06f7129922968afa Mon Sep 17 00:00:00 2001 From: Jonathan Gillespie Date: Tue, 15 Oct 2024 02:06:07 -0400 Subject: [PATCH] [WIP] --- .../core/main/logger-engine/classes/LoggerSObjectProxy.cls | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nebula-logger/core/main/logger-engine/classes/LoggerSObjectProxy.cls b/nebula-logger/core/main/logger-engine/classes/LoggerSObjectProxy.cls index ec10d94cd..1304a70af 100644 --- a/nebula-logger/core/main/logger-engine/classes/LoggerSObjectProxy.cls +++ b/nebula-logger/core/main/logger-engine/classes/LoggerSObjectProxy.cls @@ -9,7 +9,6 @@ * Each inner class maps to a corresponding `SObjectType` that is difficult to work with Apex for some reason or another, * such as not being mockable or creatable, or not existing in all orgs. */ -@SuppressWarnings('PMD.ExcessivePublicCount, PMD.PropertyNamingConventions') public without sharing class LoggerSObjectProxy { /** * @description All `Schema.AuthSession` SObjects are read-only in Apex, which makes them more difficult to work with, and impossible @@ -75,6 +74,7 @@ public without sharing class LoggerSObjectProxy { public String UniqueName; } + @SuppressWarnings('PMD.ApexDoc') private abstract class SObjectProxy { public String serialize() { return System.JSON.serializePretty(this);