-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Ft job portal refactoring #973
Ft job portal refactoring #973
Conversation
…ramakhil/Auto_Jobs_Applier_AI_Agent into ft_job_portal_refactoring
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the README needs to be totally rewritten
I believe this task #976 will handle that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposal: Enhance Plugin Management with a Clearer Pattern
Currently, our plugin management lacks a precise and structured approach, which could lead to maintenance challenges and reduced extensibility as the project scales. To address this, I propose adopting Pluggy, a lightweight and flexible framework specifically designed for plugin systems in Python.
Why Pluggy?
Provides a clear mechanism for defining and implementing plugin hooks.
Supports dynamic plugin loading and priority handling.
Simplifies plugin registration and ensures scalability.
Recommended Resources
To get started and better understand the benefits of Pluggy, here are some helpful links:
https://pluggy.readthedocs.io/
https://kracekumar.com/post/build_plugins_with_pluggy/
https://dev.to/waylonwalker/a-minimal-pluggy-example-3mp0
https://waylonwalker.com/python-pluggable-architecture/
this is out of scope, for this PR (this PR only addresses - refactoring, not focuses on plugin, but still extendable for plugin) |
Refactoring changes
PS: Linked code here is earlier versions (currently broken)