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

Cleanup - Provider migration code #930

Closed
Mzack9999 opened this issue Aug 9, 2023 · 0 comments · Fixed by #941
Closed

Cleanup - Provider migration code #930

Mzack9999 opened this issue Aug 9, 2023 · 0 comments · Fixed by #941
Assignees
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.

Comments

@Mzack9999
Copy link
Member

Describe the bug
In early versions of subfinder the providers were defined within the config file. At some point they were moved to another file providers.yaml, and some glue logic was added to guarantee a smooth migration. Such code might no longer be needed since many versions were deployed, consider removing it:

@Mzack9999 Mzack9999 added the Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity. label Aug 9, 2023
@dogancanbakir dogancanbakir self-assigned this Aug 16, 2023
@Mzack9999 Mzack9999 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Aug 18, 2023
@ehsandeep ehsandeep added this to the subfinder v2.6.3 milestone Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants