Skip to content
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

Replace bespoke plugin handling with stevedore #12

Merged
merged 1 commit into from
Nov 9, 2023

Commits on Oct 26, 2023

  1. Replace bespoke plugin handling with stevedore

    Instead of using a custom-made plugin loader, use the more powerful and flexible
    stevedore library.
    
    Also, utilize the factory pattern to handle field data generation. This refactor
    also addresses a shortcoming in the code it replaces wherein there was a hard-
    coded assumption that a single plugin would provide field configuration for BOTH
    jira and bugzilla. The new code supports separate plugins for each.
    
    Note that even though the FieldDataGeneratorFactory will create a separate plugin
    for each backend type, both plugins get their data from the same
    contrib/sample_fields.json file. This is unlikely to be the approach in any
    production use of bugjira; users will instead want to implement their own plugins
    and "advertise" them to bugjira using the stevedore entry points approach.
    eggmaster committed Oct 26, 2023
    Configuration menu
    Copy the full SHA
    4178032 View commit details
    Browse the repository at this point in the history