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

Discussion: Extension Hooks #1595

Open
pepperoni505 opened this issue Mar 18, 2022 · 4 comments
Open

Discussion: Extension Hooks #1595

pepperoni505 opened this issue Mar 18, 2022 · 4 comments

Comments

@pepperoni505
Copy link
Contributor

Currently to add any extensions to the import/export process, you must use one of the existing hooks. However, these do not cover every case of what an extension might need. While yes, one can submit a pull request to add new hooks, it's eventually going to get to a point where there are way too many hooks.

My question is if it's possible to migrate to a new system of sorts. I'm not sure what that would look like, but I'd be willing to help implement this

@scurest
Copy link
Contributor

scurest commented Mar 18, 2022

Why don't you just make a patched version of the addon? The source code could be cleaned up to make this easier (eg. using relative imports only).

@pepperoni505
Copy link
Contributor Author

I'm not really familiar with patching in python. Would you mind providing a simple example?

@scurest
Copy link
Contributor

scurest commented Mar 18, 2022

I mean forking the code and making whatever changes you want.

@elmajime
Copy link

I'm currently working on the addition of import/export hooks for extras and extensions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants