How can I activate a TagHelper when the module is enabled

[hishamco]

I'm working on a certain module, I created a TagHelper for that, which is registered when the module is enabled, my question is how can I toggle the visibility depending on module activation, something like what I have seen in most modules that are using Liquid filters

[ns8482e]

I guess you need RequireFeatures on your feature Startup

e.g. Following configures Liquid filters from Contents module only if feature OrchardCore.Liquid is enabled.

OrchardCore/src/OrchardCore.Modules/OrchardCore.Contents/Startup.cs

Lines 210 to 220 in 815e297

	[RequireFeatures("OrchardCore.Liquid")]
	public class LiquidStartup : StartupBase
	{
	public override void ConfigureServices(IServiceCollection services)
	{
	services.AddScoped<ILiquidTemplateEventHandler, ContentLiquidTemplateEventHandler>();
	services.AddLiquidFilter<BuildDisplayFilter>("shape_build_display");
	services.AddLiquidFilter<ContentItemFilter>("content_item_id");
	}
	}

[hishamco]

This will register the liquid filters when the specified feature(s) is enabled, I'm not sure if the TagHelper in the view, and not registered it will render nothing or show an error

Let me try .. thanks

[sebastienros]

I am worried with the notion of "visibility" that you mentioned.
What do you expect to happen when a cshtml is run and uses a TagHelper from a feature that is not enabled?

[hishamco]

For now I can do the check in the TagHelper, and suppress the output if the module is disabled

[ns8482e]

@addTagHelper makes tag helper available in view so if you have reference to the assembly then the tag helper is available in view/shape.

So you control the visibility of view/shape not TagHelper.

If a view is for specific feature then only add TagHelper related to that feature on that view.

MVC controller (views) can be bound to feature, but shapes are discovered on module.

I would suggest to define base shape in module and add different alternates via ShapeTableProvider defined for each feature to extend base shape. Each alternate shape/view for a specific feature will use TagHelpers intend to use for that feature.

[hishamco]

If a view is for specific feature then only add TagHelper related to that feature on that view.

Make sense, but the scenario I have to add it in the layout ;)

[ns8482e]

Tb

scenario I have to add it in the layout ;)

Layout is shape so above mentioned will work for it,

E.g. default will be Layout Feature1 will show Layout__FeatureOne and Feature2 will show Layout__FeatureTwo

Or may be you keep single Layout and inject a zone based on enabled feature.

[hishamco]

Thanks a lot, I think I need to deep dive into shapes and zones ;)

[ns8482e]

Example of this scenario - injecting Zone is AdminMenu.

[hishamco]

Exactly!!