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

Should we provide a LazyTaskAction? #395

Open
aaronayres35 opened this issue Jan 12, 2021 · 0 comments
Open

Should we provide a LazyTaskAction? #395

aaronayres35 opened this issue Jan 12, 2021 · 0 comments

Comments

@aaronayres35
Copy link
Contributor

Related to #394

In some cases, one plugin may contribute actions that reference a task contributed by a different plugin. In cases like these, care needs to be taken so that those actions don't try to access or reference that Task before it exists.

We could define a subclass of TaskAction called LazyTaskAction which waits until someone tries to access the task to define. This class could make use of the get_task method on the application as mentioned in #394

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

1 participant