Skip to content

Conversation

@ngreardSF
Copy link
Contributor

@ngreardSF ngreardSF commented Nov 24, 2024

Fixed #801 - review loadOrganizationLimits to minimise CPU usage

@ngreardSF ngreardSF requested a review from jongpie as a code owner November 24, 2024 16:35
@jongpie jongpie added optimization Layer: Log Management Items related to the custom objects & Logger Console app labels Dec 2, 2024
@jongpie
Copy link
Owner

jongpie commented Dec 2, 2024

@ngreardSF this is great! Thanks for logging #801 & submitting this PR. The pipeline doesn't automatically run for forked PRs, so I'm working on manually creating a new package version with your changes. I'm hoping to have this released either today or tomorrow 🥳

…me to include 'serializable' to provide a little more context on why there is a custom class for org limits

These were existing names (that I wrote), and having not looked at this code in a while, it took me a moment to remember why the custom class was needed. A small comment + more verbose names should help make it clear why it's needed.
Copy link
Owner

@jongpie jongpie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ngreardSF your changes look great! I added a few commits related to packaging + I renamed some variables & classes in LogHandler (mostly existing variables & classes that I had named), and I think this is ready to go!

I'll merge & release this later today.

@jongpie jongpie merged commit 9484c4b into jongpie:main Dec 3, 2024
1 check passed
@jongpie
Copy link
Owner

jongpie commented Dec 3, 2024

Released in v4.15.1 🎉 Thanks again @ngreardSF for all of your help with this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Layer: Log Management Items related to the custom objects & Logger Console app optimization

Projects

None yet

Development

Successfully merging this pull request may close these issues.

LogHandler loadOrganizationLimits intensive CPU Usage

2 participants