feat: Plugin architecture and Persistence layer #31
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 change implements Phase 4 of the codesage project, introducing a plugin architecture and replacing file-based storage with a database-backed persistence layer using SQLAlchemy.
Key changes:
PluginManagerallows dynamic loading of external Python modules that implement thePlugininterface. Users can define customRules andAnalyzers.StorageEngineclass manages database interactions using SQLAlchemy. The default database is SQLite (codesage.db), but it supports any SQLAlchemy-compatible database via connection string.Project,Snapshot,Issue, andDependencyreplace the previous flat YAML storage.codesage scancommand now accepts--plugins-dirand--db-urlarguments. It executes loaded plugins against the snapshot and saves the results to the database.SQLAlchemyandAlembic.The change ensures backward compatibility with existing snapshot generation logic while enabling advanced historical analysis and extensibility.
PR created automatically by Jules for task 18056630340618888762 started by @turtacn