Repository navigation
Replies: 2 comments 1 reply
|
there is no convention for this actually, the general way currently is to ensure they are installed and then testing the functionality |
0 replies
|
Thanks @RonnyPfannschmidt i would like to see it being a little easier, as it seems pretty common practice to defer plugins registration under certain scenarios |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Pseudo scenario:
The simplest way to achieve such a goal I can (tell) is through an ugly test, accessing private attrs like so:
Is there a cleaner way? I've had a look through the docs and nothing is jumping out.
All reactions