-
Notifications
You must be signed in to change notification settings - Fork 172
[Feature]: Split AssertLib Functionality From DebugLib #559
Copy link
Copy link
Open
Labels
impact:breaking-changeRequires integration attentionRequires integration attentionstate:backlogIn the backlogIn the backlogstate:needs-triageNeeds to triaged to determine next stepsNeeds to triaged to determine next stepstype:feature-requestA new feature proposalA new feature proposalurgency:mediumImportant with a moderate impactImportant with a moderate impact
Metadata
Metadata
Assignees
Labels
impact:breaking-changeRequires integration attentionRequires integration attentionstate:backlogIn the backlogIn the backlogstate:needs-triageNeeds to triaged to determine next stepsNeeds to triaged to determine next stepstype:feature-requestA new feature proposalA new feature proposalurgency:mediumImportant with a moderate impactImportant with a moderate impact
Type
Fields
Give feedbackNo fields configured for issues without a type.
Feature Overview
Today, assert functionality lives inside of DebugLib, which is mixing two separate features into one library and requires every DebugLib implementation to change in response to changes to assert functionality.
Solution Overview
A cleaner and more maintainable architecture would be to split the assert functionality into an AssertLib with a well defined interface that can be consumed by DebugLib.
Alternatives Considered
No response
Urgency
Medium
Are you going to implement the feature request?
I will implement the feature
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response