Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including
Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
The best answers are voted up and rise to the top
3 years, 4 months ago
Create and Upload Patches documentation, there is no mention of restrictions on adding inner classes to an already packaged top-level class. The restrictions listed are:
You can’t add package components.
You can’t delete existing package components.
API and dynamic Apex access controls can’t change for the package.
No deprecation of any Apex code.
You can’t add new Apex class relationships, such as extends.
You can’t add Apex access modifiers, such as virtual or global.
You can’t add new web services.
You can’t add feature dependencies.
public inner class be added to a managed package patch version?
Jan 25, 2020 at 12:16
Keith C Keith C
134k 24 24 gold badges 188 188 silver badges 402 402 bronze badges
Yes. We have taken this approach with our managed package when back-porting features to patches that added new top-level classes in our master branch. Obviously there are limits to what can appear in an inner class compared with a top-level one, but we have avoided such difficulties with minor refactoring.
Jan 25, 2020 at 14:12
Phil W Phil W
32k 3 3 gold badges 38 38 silver badges 81 81 bronze badges
log in to answer this question.
Not the answer you're looking for? Browse other questions tagged
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our
Accept all cookies
Necessary cookies only