architecture.yml
architecture.yml
| Title | Labels |
|---|---|
| [Architecture] | architecture, design |
Architecture discussion
Use this template for internal design decisions: changes to the suite-loading mechanism,
the coverage engine, DDL trigger behaviour, reporter infrastructure, or any
cross-cutting concern that affects the internals of utPLSQL.
This category is primarily for contributors and maintainers.
If you want to propose a user-facing feature, use RFCs & Design instead.
Which internal component or subsystem does this discussion concern?
Briefly describe how the relevant part works today.
What specific decision needs to be made, or what limitation needs to be addressed?
List the design options you are weighing. For each option describe:
- How it works
- Pros
- Cons
- Impact on Oracle compatibility
If you already lean toward one option, say so and why. Leave blank if genuinely open.
If breaking, describe the migration path for users and downstream integrations.