[analyzer_plugin] FooMixin classes are not mixins #61768 #61775
   Closed  
     +170   −122      
   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.    
 
This PR converts AssistContributorMixin (and similar utility classes like DartAssistsMixin) from abstract classes to proper Dart mixins.
Previously, these classes were marked for use only as mixins, but the analyzer produced class_used_as_mixin errors because they weren’t declared with the mixin keyword.
This change modernizes the code, allowing clients to mix them in without warnings, while preserving the original API intent (not extending or implementing them directly).
Optionally, on AssistContributor can be added for additional type safety to restrict mixin usage to subclasses of AssistContributor.
Benefits:
Removes analyzer diagnostics for clients using these mixins.
Aligns the implementation with Dart’s current best practices.
Prepares the API for safe usage in analyzer plugins.
Related Issues:
N/A (or link a relevant issue if one exists)