Support initialization directly on Blueprint Group

[ahopkins]

#181

[jekel]

Hello, can you give some suggestion how to implement this logic in the best way?
iterate over all blueprints in BlueprintGroup and initialize jwt on each?
there is also problem - how to access app.config - it is not available directly from group, it could be taken only from any blueprint.. can be in one group blueprints from different apps?

[ahopkins]

can be in one group blueprints from different apps?

Yes. 🤔

I would love to add this, so if you are interested in working on it, I am happy to help you. TBH, I have not put much thought into this lately. Iterating over each BP might work, but I would wonder what impact that would have. It does raise questions: should they have a shared config or not? where to store the Initialize instance? On the bp.ctx?

[jekel]

I think, that, for first time, we can make blueprint group support available when only one App is used, otherwise it will be harder to implement and take more time for develop..
i will try to implement it in such way and make pull request next days

[ahopkins]

I think, that, for first time, we can make blueprint group support available when only one App is used, otherwise it will be harder to implement and take more time for develop..

i will try to implement it in such way and make pull request next days

that seems a fair restriction.

[ahopkins]

Just make sure that when someone tries to attach to a BP group, we check the Sanic registry size (it's a class variable) that we raise an appropriate exception.