This repository has been archived by the owner on Apr 28, 2019. It is now read-only.
fix: implement solution for top-level @isTest and inner classes without access modifiers being ignored #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
initially reported here by @Patlatus. Top level class without access modifiers (must be
@isTest) and inner classes without access modifiers, both assumed to be private by apex, were being ignored by ApexDoc. This implements a solution for this issue. Now both forms are documented and assumed to be private. However, the fact the the top-level classes must be@isTestis still not captured. Eventually, it would be nice to capture this and other class/method annotations such as@AuraEnabled,@future,@TestVisible, etc.