-
Notifications
You must be signed in to change notification settings - Fork 3.2k
chore(plugins): Convert All Plugins Using entity-registry to Spring Configuration #14181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅ ❌ Unsupported file formatUpload processing failed due to unsupported file format. Please review the parser error message:
|
✅ Meticulous spotted 0 visual differences across 1435 screens tested: view results. Meticulous evaluated ~8 hours of user flows against your PR. Expected differences? Click here. Last updated for commit a5559cb. This comment will update as new commits are pushed. |
Bundle ReportChanges will decrease total bundle size by 37.52kB (-0.17%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: datahub-react-web-esmAssets Changed:
|
This PR completes the migration of all remaining plugins from YAML configuration in entity-registry.yml to Spring beans, unifying the plugin management system under Spring's dependency injection framework. 8 plugins have been successfully migrated across aspectPayloadValidators, mutationHooks, and mcpSideEffects categories, including CreateIfNotExistsValidator, ConditionalWriteValidator, FieldPathMutator, OwnershipOwnerTypes, StructuredPropertiesSoftDelete, PropertyDefinitionValidator, StructuredPropertiesValidator, and PropertyDefinitionDeleteSideEffect. All plugins now follow a consistent Spring bean pattern in SpringStandardPluginConfiguration.java with proper AspectPluginConfig setup and corresponding test coverage, providing better type safety, compile-time validation, and unified configuration management while maintaining full backward compatibility and functionality.