How to exclude or lazyload a presenter

@materix

Yes, Nette developers sometimes need the possibility to prepare a “concept” of presenter or disable existing presenter which would be invisible for DI, because the class contains errors and work on it will be done later. I think this feature is missing in Nette DI, but would be very useful. One possibility is to add to nette/application attribute #[Disabled] applied to final presenter class like this:

#[Disabled]   // attribute makes presenter invisible for DI
class ArticlePresenter extends BasePresenter
{
   // some code with errors, we plan correct later
}

nightfish wrote:

It is possible to exclude a presenter from DI?

@materix How about making the presenter class abstract?

Thanks for the work-around idea, which does work.

dkorpar wrote:

Why not having all that in seperate branch and when you're done you put it out? Having code in master which is WIP or does not work does not sounds good IMHO.

Thanks for the suggestion. In this case I have multiple WIP-presenters that are not ready, and I want to be able to test the code while coding. But the app is failing because of DI.

Currently using @nightfish suggestion and changing them to abstract classes.

For Hotfix, just switch branch and then go back to previous branch. The workaround with “abstract” seems to be sufficient, even that should not be needed often (almost never).
I would be careful with the new annotations, you have to remember them because they are not a standard feature of the language.