| [Feature] | feature-request |
Use this category for feature ideas specific to the utPLSQL framework: new matchers, annotation behaviour, reporter output, suite control, coverage, or installation.
For ideas that affect multiple components or the project direction overall, use org-level Feature Requests instead.
A maintainer will mark this discussion as answered once the proposal is accepted or declined.
If accepted, a maintainer will convert it to an issue for implementation tracking -- you do not need to open an issue yourself.
What problem does this feature solve? What is the current limitation or pain point?
Describe the feature you have in mind. Include examples of how it would be used, ideally with PL/SQL annotation or API examples.
Have you found any alternative approaches or partial workarounds?