Trigger support #240
Merged
Trigger support #240
Conversation
This file contains hidden or 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
Apex triggers. Triggers are now parsed and documented alongside classes and custom objects.
The commit makes two main changes: 1. Formats trigger event names with proper capitalization 2. Improves trigger template layout by renaming "Events" to "Run" The changes also include some automatic path updates in the VitePress configuration files.
The new test cases validate that the changelog generator properly handles: - New trigger additions with object context - Trigger removals with object context - Unchanged triggers being excluded
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduces support for parsing and documenting Triggers